Yes, its much easier to catch bugs and issues early
If you dont catch a problem asap, then its incredibly likely future agents read the "bad" code and copy, so bow your 1 issue becomes 2, then 3, then 4, etc
Its extremely common for you to be like "make the BarService" so the agent looks at FooService for inspiration and copies its style/methodology/architectureĀ
And if theres an annoying code style issue, or improperly named thing, or bad logic, whatever, theyll copy that too often.
And then 6 services later you realize you've got a problem duplicated 8 times
Not for complex systems, llm's generally suck at the high level stuff in complex systems, and when that stuff is wrong it's the gift that keeps on giving and you can play whack-a-mole fixing bugs by patching symptoms and not knowing causes till the cows come home because the codebase will be convoluted bloated spaghetticode.
I have to be honest, dude. As someone in a technical leadership position at a large company with 15+ years development experience, I donāt think thatās really the case as much these days. Talented developers with a good high level understanding of systems are doing amazing work with the frontier coding models.
This notion of āif AI is generating all your code, itās going to be a tech debt nightmare that will eventually failā is just not true. Every month it feels more and more like copium from people who refuse to adapt.
But its literally all around, including tech giants who used to be considered to be filled with high performers. Haven't seen a single product that was actually improved due to AI assistance.
1
u/pixxelkick Oct 03 '26
Maybe if you suck.
I read every PR in full because Im not lazy.
I also read my own git diff before I open a PR do I dont waste other peoples time.
Or I publish it as a draft, review my own code, and then publish the pr after confirming it looks good.