Re:Harvard researchers find AI coding agents shifted the bot...
by hibikir on Tuesday November 17, 2026 @09:10PM
(#50541000)
We were there many years ago too though: I had to take over a rather complicated system circa 2012, which had been designed to be built by a team of 20 or so, for timelines, but they had little effort on integration. This meant that a whole lot of guards were written all over the place for situations that, in practice, never occurred. To try to get this to production in a timely fashion, I ended up putting metrics per guard, along with metrics for what was caught by broad error checks near the base of the program. Basically all the defensive programming that had been built was pointless, while I had to write a whole lot of cases that were being dropped, and the people that designed things up front never considered.
AI error handling in code review is a lot like said defensive programming in a vacuum: It'll take a lot of code and a lot of energy, but it's unlikely to be important. Even when you are designing something that gets executed hundreds of millions of times a minute, over-review is easy. You pay for it when letting errors in the real world are unacceptable, but it's pretty inefficient. And that's without getting into features that just don't get used, so the entire thing should not have been built in the first place.
AI error handling in code review is a lot like said defensive programming in a vacuum: It'll take a lot of code and a lot of energy, but it's unlikely to be important. Even when you are designing something that gets executed hundreds of millions of times a minute, over-review is easy. You pay for it when letting errors in the real world are unacceptable, but it's pretty inefficient. And that's without getting into features that just don't get used, so the entire thing should not have been built in the first place.