Re:Software is breaking down at a systemic level
by dbg31415 on Monday November 16, 2026 @03:29PM
(#50522778)
It's nice to say, "Oh we did it better in our day! You kids lack discipline!"
But look, the reality is we copy-pasted just as much slop we didn't really understand to get over the finish line back then as kids to today.
Deadlines were missed. There were bugs. Things broke. That's just life.
Now, do I wish we had TDD for everything? Yes. Do I wish there wasn't quite as much emphasis on AI? Also yes.
But there's a literal mountain of slop code that was written over the last 40+ years. Without AI, it sort of just sits there... people are afraid to touch it.
With AI, and I mean me using AI, I'm comfortable diving into a massive legacy code base and refactoring pretty much anything at will. And it's pretty cool when you stop looking at code as "I don't want to be the last one to touch it, because then I'll get blamed if it breaks."
And instead take the approach, "OK, without proper maintenance, this dies. How can I give it proper maintenance?" And look, if something breaks along the way, "Meh." I can fix it. Those old code bases were often just as buggy and duct-tapped as anything AI created... worse... years upon years of multiple developers doing patches. Convoluted AF.
I still like to think I have good discipline. I have a repo that has all my coding standards, and that's a good starting point for most of my projects. I weave in a bunch of rules as I go, things I learn, and that repo becomes the guide for the AI to do work on the project I'm working on. Then... when I'm not the one doing the work, it'll still be there to explain to the next person (or rather AI being managed by a person) why I did things, and what the goals were, and how shit works.
Most things that break... it's just because it wasn't documented in the first place. I find a lot of that... maybe they had discipline, and maybe the legacy systems that had the documentation were lost to time. Sure. Let's give them the benefit of the doubt. But... I'm guessing they did quite a few patches with just someone calling, "Hey Swanson, make the button blue, and make it say 2+2=7 to impress this client!" Right, so there's still a lot of that today too.
But look, the reality is we copy-pasted just as much slop we didn't really understand to get over the finish line back then as kids to today.
Deadlines were missed. There were bugs. Things broke. That's just life.
Now, do I wish we had TDD for everything? Yes. Do I wish there wasn't quite as much emphasis on AI? Also yes.
But there's a literal mountain of slop code that was written over the last 40+ years. Without AI, it sort of just sits there... people are afraid to touch it.
With AI, and I mean me using AI, I'm comfortable diving into a massive legacy code base and refactoring pretty much anything at will. And it's pretty cool when you stop looking at code as "I don't want to be the last one to touch it, because then I'll get blamed if it breaks."
And instead take the approach, "OK, without proper maintenance, this dies. How can I give it proper maintenance?" And look, if something breaks along the way, "Meh." I can fix it. Those old code bases were often just as buggy and duct-tapped as anything AI created... worse... years upon years of multiple developers doing patches. Convoluted AF.
I still like to think I have good discipline. I have a repo that has all my coding standards, and that's a good starting point for most of my projects. I weave in a bunch of rules as I go, things I learn, and that repo becomes the guide for the AI to do work on the project I'm working on. Then... when I'm not the one doing the work, it'll still be there to explain to the next person (or rather AI being managed by a person) why I did things, and what the goals were, and how shit works.
Most things that break... it's just because it wasn't documented in the first place. I find a lot of that... maybe they had discipline, and maybe the legacy systems that had the documentation were lost to time. Sure. Let's give them the benefit of the doubt. But... I'm guessing they did quite a few patches with just someone calling, "Hey Swanson, make the button blue, and make it say 2+2=7 to impress this client!" Right, so there's still a lot of that today too.