Our leadership is not pushing us to skip dev review. We have AI coding guidelines where engineers are trusted to merge in pull requests with no review if they pass certain criteria. Our code reviews are more so reviewing architectural docs, plans, evaluation criteria, etc. that an AI would then write the code for later.
You've reached the end!
is_the_grass_gr•3h ago
The other devs have already torpedoed standups and now no one wants to code review anymore. I'm sitting here remembering at the start of my career how people had to advocate for version control and code review and now my head is spinning because we're about to abandon it in favor of AI writing the code and AI reviewing it.
I maintain that code review is about having one another's back more than being a hoop to jump through, and that the rest of the folks in the employ of the company depend on our diligence. But I also am keeping note that all the "fixes" are on the reviewers side rather than the onus being on the dev requesting review. In my opinion, it's easier than ever to make a clean branch with clear atomic commits with good commit messages, and not knowing how to rebase is no longer an issue. But still the PRs are messy and large.