As someone who made a reasonable reputation for himself by being a meat proxy for google search for years (Hey, go ask him, he knows about loads of stuff...) I'm surprised anyone even notices if others are just doing auto-reviews.
> I always saw the software engineering field as being comprised of two groups of people: people who are devs because they are passionate about building software, and people who don't actually enjoy software but joined the field because it's a job that pays well.
There's a third motivation hiding in there, people who were passionate about coding, rather than building software. It's a subtle difference but an important one. Folks whose primary focus is building and delivery are having a field day with LLMs because they've found a way to build and deliver in far less time with far less resource. Folks who have been more passionate about the coding itself are finding that their legs have been shot out from under them, because what they enjoyed and where they thought their value lay is becoming less relevant.
I absolutely get the frustration here, but conversely I think some companies now are seeking to remove the human from the loop as much as possible. That interactive AI-assisted workflow? That's a mid-state, why not instead have a multi-stage automation pipeline, to digest a set of requirements, build granular jira tickets for the work, come up with acceptance criteria, implement test harness additions for those, build the code, test it, iteratively review the code from several different viewpoints (security, minimalism, performance etc), and post it as a PR? Sure, you probably want a plan-review checkpoint, and the agents should stop and ask when they need to know something from their human overseers, but ... we're going more automated in general.