Re:Verification debt: the hidden cost of AI-generated code
by xantronix on Saturday March 07, 2026 @03:56PM
(#47291409)
I can't help but think that the logical conclusion of spec-first development is a return to Waterfall methodology. The amount of rigour required almost entirely negates the speed advantages of LLMs, even in the hands of seasoned developers. Unless the stakeholders are external, there will always be that necessary organisational bottleneck; of course, the C-suite could always decide to foist project management entirely on individual contributors, or take it on themselves, but I see that ending either in burnout or eventual neglect. All in the service of being on the forefront of adoption, and for what end?
[ Parent
| on HN ]
Re:Verification debt: the hidden cost of AI-generated code
by dwb on Saturday March 07, 2026 @04:35PM
(#47291685)
Yeah, agree. Either that or this idea of not reviewing the code at all takes hold, abdicating human engineering responsibility to the machines, until some big stupid disaster or when it’s Too Late.
Re:Verification debt: the hidden cost of AI-generated code
by whattheheckheck on Saturday March 07, 2026 @08:59PM
(#47293564)
Is the teleological fight. Do swe decide what the purpose of the system is or do non technical people?
Intention flows are important
Re:Verification debt: the hidden cost of AI-generated code
by dwb on Sunday March 08, 2026 @04:10AM
(#47295529)
I’m not talking about which humans decide the purpose of the system, or even which humans engineer the system once designed at a higher level. I’m worried about leaving crucial decisions and understanding to LLMs, with humans just stepping back.