I think the points about code ownership and responsibility are spot on. Management wants you to increase velocity with these agents so inevitably there is pressure to ship crappy code. You then will be responsible for the code, not the AI. It’s the idea of being a reverse centaur.

I also like the comments on how developers should be frequently reading the entire code and not just the diffs. But again there is probably pressure to speed up and then that practice gets sacrificed.

If your Management thinks it's acceptable to increase velocity by shipping crappy code, I'm surprised they never thought to do this before AI.

From what I've seen, companies using AI well are shipping better code because of all the artifacts (supporting context like Architectural Design Records, project-specific skills and agents, etc.) and tests needed to support that. I understand that many are not using AI well.

> there is pressure to ship crappy code

this is true with or without AI

The rush it out the door mentality of this industry is stupid.