When generating code gets cheaper, the scarce activities become deciding what to build, checking that it is right and keeping the system understandable.
Shifts to plan for
- Specifications matter more — clear requirements and acceptance tests guide both people and tools.
- Review capacity becomes the bottleneck; invest in automated checks and smaller changes.
- Test coverage becomes a safety net for generated code.
- Security review must cover generated dependencies and patterns.
- Junior engineers still need to learn by doing real work with feedback.
Measure delivery outcomes such as lead time, failures in production and rework, not lines of code produced.