Both. AI code review is built-in, but there's always a second human in the loop.

I'm concerned that there are people pushing on the code generation front, the code reviewing front, and the laziness front. Eventually they're going to all meet in the middle, and there will be a significant number of engineers who are using AI to write and review the code, rubber stamp it, and push it into prod, with disasterous results.

No code review here. I tried to make it a regular part of my work flow but, it didn't last. That being said, I'm a retired developer and everything I build are personal projects so the stakes are lower than for working developers. I retired just a year or two before AI coding agents came into existence so I never experienced using these tools in an actual workplace setting. Working must have a whole different vibe these days

Increasingly not. We use CodeRabbit at work, which catches good stuff. And I have my own gauntlet that I run code through.

https://github.com/jacquardlabs/gauntlet

I wonder how codebases for important products (not demos or short-living ones) end up without anyone reviewing the code. Some claim engineers should become more of "architects" and "designers", but not coders/reviewers anymore. Wish to hear people's stories, if much documentation and reviewing from the high-level only is enough to keep the project from becoming a failure

Nope. I occasionally do human review of my own code and very occasionally of other peoples', but for the most part it's all 100% automated. I use Codex's Github code review integration and it does a pretty decent job of spotting P1's and P2's.

[flagged]