What I find interesting about this are the things the specific example leaves out. Many engineers consider code reviews a real drag, but they aren't just busywork or wasted time or compliance checkboxes. Done well, they are a learning tool, a teaching opportunity, and a form of communication between engineers working in different areas of the code at different skill levels and knowledge levels. All of those things have value and add to team productivity in the long term. The "cost" in terms of hours spent doing code reviews is not wasted. But if you turn that job over to AI (even if you could), you lose almost all the benefits, adding a drag on your future productivity as knowledge gaps grow and communication declines.<p>On the other hand, if you're doing code review poorly, and it's just a waste of everyone's time, then you're far better off just dropping them altogether than spending money on an AI system to do poor code reviews for you.