this post was submitted on 27 May 2025
74 points (96.2% liked)

Programming

20415 readers
261 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 4 days ago (1 children)

"The problem isn’t just laziness. It’s degradation. Engineers stop exploring. Stop improving. Stop caring. One more layer of abstraction. One more lazy fetch call inside a render loop. Eventually, you’re living in a cathedral of technical debt, and every user pays."

This quote has the no one wants to work anymore vibe.

We all predicted this when web frameworks and object relation mappers were introduced... And we were right... Kind of. The average programmer is certainly worse - but there's also many more of us, getting a lot more done. And there's still plenty of us who master the craft.

[–] Senal 6 points 3 days ago

The differences here are that ORM and web frameworks weren't actively making the job harder and the sheer surface area of the problem.

If you fuck up with a framework or an ORM, it generally just fails to work, the magic internals might not be super helpful with their error messages, but such is the nature of the tradeoffs.

If you fuck up with an LLM you get something that generally compiles and looks like it should work, that's much more of a problem for both you and anyone who then needs to go trawling through, looking for the issues.