>Your job is to design, the AI builds like the junior engineers. Then you review their work.
I'll add to this that your job is also to design tooling and feedback loops that allows the AI to improve over time.
You have policy gates: How the AI should act. (and a feedback loop to check the code is adhering to those policy gates)
You have quality gates: How the AI verifies it's done things correctly (testing, linting, PRDs, cyclomatic complexity)
Modern AI engineering is really about improving this system rather than manually reviewing AI output. The better the policy gate and quality gate enforcement, the less manual review is required and the more velocity you achieve.
Sticking with being a human-in-the-loop reviewer of AI code is where people lose all hope in still being software engineers.
I'll add to this that your job is also to design tooling and feedback loops that allows the AI to improve over time.
You have policy gates: How the AI should act. (and a feedback loop to check the code is adhering to those policy gates)
You have quality gates: How the AI verifies it's done things correctly (testing, linting, PRDs, cyclomatic complexity)
Modern AI engineering is really about improving this system rather than manually reviewing AI output. The better the policy gate and quality gate enforcement, the less manual review is required and the more velocity you achieve.
Sticking with being a human-in-the-loop reviewer of AI code is where people lose all hope in still being software engineers.