How are you managing code reviews in the AI era?
We’ve noticed that most of our tickets are getting stuck at the code review stage, mainly because PRs have become so large that they take much longer to review!
I’m curious to hear how you’re handling this in your team!
Commit
04ee0fa
I was at the TYPO3 Camp in Berlin in October, one developer presented her workflow with Herdr. She lets her work develop with one AI (Brain) and reviewed with another (don't recall what she called it).
But the two models are trained differently, and the review one strict in…
We’re trying that, and it works for catching some obvious issues, but it misses the more complex ones, like orchestration between services, or even simpler things like ensuring the correct order of migrations and deployments.
There’s also a more concerning issue: we gradually lose track of how the product actually works, including its internal workflows and business logic. Eventually, the product becomes a “black box” written by AI that you have to reverse-engineer every time you want to add a new feature or fix a bug.
commit 04ee0fa
I'm completely with you on the concerns, I'm not for all AI development, I want some control my self.