• Sign in
  • Sign up
Elektrine
EN
Log in Register
Modes
Overview Chat Timeline Communities Gallery Lists Friends Email Vault DNS VPN
Back to Timeline
  • Open on lemmy.world

keegomatic

@keegomatic@lemmy.world
lemmy 0.19.17-8-gded733659
0 Followers
0 Following
Joined June 29, 2023

Posts

Open post
Boosted by Technology @technology@lemmy.world
In reply to
keegomatic
@keegomatic@lemmy.world
lemmy.world
keegomatic
keegomatic
@keegomatic@lemmy.world
lemmy.world
@keegomatic@lemmy.world in technology · Dec 10, 2025
violates licenses Not a problem if you believe all code should be free. Being cheeky but this has nothing to do with code quality, despite being true do the thinking This argument can be used equally well in favor of AI assistance, and it’s already covered by my previous reply non-deterministic It’s deterministic brainstorming This is not what a “good developer” uses it for
View full thread on lemmy.world
0
0
0
0
Open post
Boosted by Technology @technology@lemmy.world
In reply to
keegomatic
@keegomatic@lemmy.world
lemmy.world
keegomatic
keegomatic
@keegomatic@lemmy.world
lemmy.world
@keegomatic@lemmy.world in technology · Dec 08, 2025
We have substantially similar opinions, actually. I agree on your points of good developers having a clear grasp over all of their code, ethical issues around AI (not least of which are licensing issues), skill loss, hardware prices, etc. However, what I have observed in practice is different from the way you describe LLM use. I have seen irresponsible use, and I have seen what I personally consider to be responsible use. Responsible use involves taking a measured and intentional approach to incorporating LLMs into your workflow. It’s a complex topic with a lot of nuance, like all engineering, but I would be happy to share some details. Critical review is the key sticking point. Junior developers also write crappy code that requires intense scrutiny. It’s not impossible (or irresponsible) to use code written by a junior in production, for the same reason. For a “good developer,” many of the quality problems are mitigated by putting roadblocks in place to… force close attention to edits as they are being written, facilitate handholding and constant instruction while the model is making decisions, and ensure thorough review at the time of design/writing/conclusion of the change. When it comes to making safe and correct changes via LLM, specifically, I have seen plenty of “good developers” in real life, now, who have engineered their workflows to use AI cautiously like this. Again, though, I share many of your concerns. I just think there’s nuance here and it’s not black and white/all or nothing.
View full thread on lemmy.world
0
0
0
0
Open post
Boosted by Technology @technology@lemmy.world
In reply to
keegomatic
@keegomatic@lemmy.world
lemmy.world
keegomatic
keegomatic
@keegomatic@lemmy.world
lemmy.world
@keegomatic@lemmy.world in technology · Dec 08, 2025
You’re wrong, whether you figure that out now or later. Using an LLM where you gatekeep every write is something that good developers have started doing. The most senior engineers I work with are the ones who have adopted the most AI into their workflow, and with the most care. There’s a difference between vibe coding and responsible use.
View full thread on lemmy.world
0
0
0
0
313k7r1n3

Company

  • About
  • Contact
  • FAQ

Legal

  • Terms of Service
  • Privacy Policy
  • VPN Policy

Email Settings

IMAP: mail.elektrine.com:993

POP3: pop3.elektrine.com:995

SMTP: mail.elektrine.com:465

SSL/TLS required

Support

  • support@elektrine.com
  • Report Security Issue

Connect

Tor Hidden Service

khav7sdajxu6om3arvglevskg2vwuy7luyjcwfwg6xnkd7qtskr2vhad.onion
© 2026 Elektrine. All rights reserved. • Server: 07:12:27 UTC