this post was submitted on 27 Mar 2026
61 points (95.5% liked)

Programming

26250 readers
607 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 !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
61
Thoughts on slowing the fuck down (mariozechner.at)
submitted 17 hours ago by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev
6 comments fedilink hide all child comments
 

[...] Coding agents are now also introduced to production codebases. After 12 months, we are now beginning to see the effects of all that "progress". Here's my current view.

[...]

All of this compounds into an unrecoverable mess of complexity. The exact same mess you find in human-made enterprise codebases. Those arrive at that state because the pain is distributed over a massive amount of people. The individual suffering doesn't pass the threshold of "I need to fix this". The individual might not even have the means to fix things. And organizations have super high pain tolerance. But human-made enterprise codebases take years to get there. The organization slowly evolves along with the complexity in a demented kind of synergy and learns how to deal with it.

With agents and a team of 2 humans, you can get to that complexity within weeks.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] HaraldvonBlauzahn@feddit.org 17 points 17 hours ago* (last edited 16 hours ago) (1 children)

And organizations have super high pain tolerance.

The organization slowly evolves along with the complexity in a demented kind of synergy and learns how to deal with it.

That rings so true.

But the thing is, pain is a warning signal. If you go jogging completely drunk and hit a tree with 6 mph, it will be painful, yes, but the pain will warn you not to do it again.

But what if you move 12 times faster?

If you drive a light motorcycle completely drunk and with no helmet, and hit a tree, pain will not be able to save you.

For company legacy codebases, yes they are dysfunctional but they have found a kind of precarious equilibrium in so far as they exist because they are making money and thus are useful by some metric. The slow movement and requirement to work somehow balances the unstoppable (with in company practices) growth of entropy and messiness.

And in a way, the money is an analgetic for the pain. Or more sharply, big companies act like junkies on a money drug because money is the only thing that ever counts.

Figure what happens if entropy is grown 100 times faster...

[โ€“] jimmy90@lemmy.world 1 points 12 hours ago

if you don't know how to make good code you can't expect AI to do it either

if you can code well then AI can be a great help