I don’t doubt that it is possible to create good code when focusing on programming best practices etc. and taking the time to check the AI output thoroughly. Time however is a luxury most of the devs in those companies don’t have, because they are expected to have a 10x code output. And thats why the shit hits the fan. Bad code gets reviewed under pressure, reviewers burn out or bore out and the codebase deteriorates over time.
But we have to identify this as what it is: an internal policy failure where they abandon proven processes to maintain code quality.
I guess I’m lucky my managers have not put that pressure on me yet. I do however see developers getting sloppy and lazier so the reviews actually do take more effort and AI rarely catches all problems with a change.
I don’t doubt that it is possible to create good code when focusing on programming best practices etc. and taking the time to check the AI output thoroughly. Time however is a luxury most of the devs in those companies don’t have, because they are expected to have a 10x code output. And thats why the shit hits the fan. Bad code gets reviewed under pressure, reviewers burn out or bore out and the codebase deteriorates over time.
But we have to identify this as what it is: an internal policy failure where they abandon proven processes to maintain code quality.
I guess I’m lucky my managers have not put that pressure on me yet. I do however see developers getting sloppy and lazier so the reviews actually do take more effort and AI rarely catches all problems with a change.