Perhaps the velocity is the problem, not that AI inherently produces worse code (you just need one bad or just inexperienced engineer have their PR slip through to have bad human written code in you code base). When the velocity is high, there's less time to battle test each change and new code piles up on the old one. When the velocity is low, shitty code fails in production, but people are aware of what was recently changed and can find and fix the problems.

▲

_kulang a day ago | parent | next [-]

Same thing, now, just faster: one bad engineer can now ship a million lines

	▲	karmakurtisaani a day ago \| parent [-]
		Well, yes. My point was more that even if the quality was better, the speed of change is a problem. In particular in mature systems, I should add.

▲

dabinat a day ago | parent | prev [-]

For some reason people seem to think that just because AI exists now, code no longer needs testing thoroughly.

	▲	karmakurtisaani a day ago \| parent [-]
		Yep, and having a ton of AI written unit tests pass is not the same as running incident free in production for a month.