News for hackers. Stuff that matters.

techdebtgoingaw

Re:AI usage generates a fragile codebase on Tuesday November 10, 2026 @10:01PM (#50449294)
I like this take for the same reason I liked the <AI is forcing us to pay back decades of tech debt> articles.

Even if AI did indeed make worse architectural decisions, that just means we have to be more on top of it in preventing them to make those decisions.

We've already managed to successfully convince everyone that you should tell AI to always produce tests for your changes. But we were ALWAYS meant to ALWAYS have test. Why did we ever not do that? Oh right, lack of time, different priorities, etc. etc. AI gives us the time back so now we're no longer allowing excuses. Weird how the standards only change with a complete lack of care and naive trust of AI?

The article also mentions that AI produces code that doesn't scale. Well? Why aren't you running a profiler and looking for places to optimize then? You were ALWAYS meant to do that. You were ALWAYS meant to ~prove~ the scalability of your architecture. This was ALWAYS a responsibility of engineers. Why are you just trusting it to do whatever instead of putting in the work doing all those things and improving? Where the hell did your responsibilities go, and why are we having a discussion on AI instead of on the fact the human is avoiding their job-description responsibilities?

I am an engineer. It is my job to produce good code. And I am proud of that, and of what that means. And right now, that means looking at AI doing a half baked job, and either baking the other half myself, or telling the AI how to.

Knock knock. That's all the shitty engineering of the last decades. It isn't dead. It's just called vibecoding now. Don't blame the AI. Unmask it, and blame shitty engineers.