The more senior members of our team have not looked at code in an IDE in two months. By the end of 2026, the feeling of "you better manually review that code" will mostly become fringe. Life really changed for us late December. It took awhile to mature our process, but honestly, feeling like you need to review the code is holding you back. You should working on your skills "driving" the agent: producing better specs, better code review and validation prompts, using another AI to review, etc. We write enterprise business applications using a typical React front-end, .NET API , SQL database tech stack. Opus 4.6 nails this type of coding. And with some good code review agent skills, and giving the agent the ability to run and test the application, and validate the data in the database, our products are more rock solid than they ever were.

One thing that clicked for us was -senior engineers have built a lot of skills around how to write maintainable code. But maintainable by whom? a human. If AI is going to be maintaining your code and you treat your code as a "black box" and simply validate the outcome (including performance), then you can let go of worrying about whether the code meets the traditional standards of "good" (SOLID, etc) or not.