The reverts will continue until morale improves

I mean

But there was also a long tail of relatively harmless issues involving various edge cases. In past times, many of these would not have surfaced until much later and we would have fixed them bit by bit over the subsequent five years. But with LLM-assisted code review, these kinds of things can get found much faster, and then you’re staring at a list of like forty defect reports. And even if each of them requires only a three-line fix on average, there is a fixed overhead to dealing with each of these, and then you run out of time. Most if not all of the affected reverted features were written a long time ago when LLM-assisted code review was not as useful as it is now, meaning that the effective quality bar has been raised after the time the feature was written and committed.

and then

A corollary of that is that, at least for the most part, as far as I can tell, this situation is not due to “vibe coding”. This code was written well before that was a possibility.

I think this is a fair explanation? That is:

• The code is human-written, if not just because at the time the relevant code was written LLMs were even worse at writing code, so it does truly not fall under the usual definition of "vibe coding".
• LLMs are relatively good at finding bugs, as has been widely documented, e.g. from the curl maintainer. Of course, there are entities that would like to exaggerate this for marketing, but fundamentally there are many bugs that aren't that novel but still escape human eyes due to being deep within large amounts of code. So it's not unsurprising that an LLM could find issues in what I expect to be some pretty complex database innards.

We've had vibe code for like three years now. Surely at least it was a possibility...