70
Thoughts on slowing the fuck down
(mariozechner.at)
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
Follow the wormhole through a path of communities !webdev@programming.dev
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...
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