Have a single human AI chef. Everyone else has to write an engineering statement and submit it to the AI chef. All that interaction is outside the codebase. Engineers will take turns - perhaps 1 month stints - being the AI chef.
replyI guarantee you'll spend less on tokens, have better documentation, better code, and most importantly more competent engineers.
That's like asking "how do you build competence in plowing a field with a horse in a world of tractors"
replyPretty straight forward really, you keep using horses in parallel: https://www.abc.net.au/news/2025-10-18/heavy-horsemen-keep-f...
replyThat's the other side of the country, but it's how it's done over here also.
Still pull the old plough varieties, still practice shed blacksmithing, etc - even while developing and using autonomous Ag-Bot tractors for spraying, etc.