The Second Apprenticeship: Surviving AI in Engineering
Summary
The advent of generative AI is bifurcating the software engineering profession, with employment for developers aged 22 to 25 down nearly 20% since its arrival, while engineers over thirty in high-exposure jobs have seen a 6% to 12% gain. This divergence stems from AI's propensity to generate "slop" – poor quality code – at machine speed, leading to 1.7 times more issues per pull request and a 30-40% increase in technical debt in AI-managed repositories. The author, Anatoly Volkhover, argues that AI excels at following rules but lacks architectural judgment, which involves complex trade-offs and understanding system lifecycle costs. He proposes a "second apprenticeship" for architects to master "Agentic Spec-Driven Development," a methodology where AI is precisely steered by explicit rules and specifications. This approach transforms AI into a highly productive, rule-following developer, enabling architects to maintain quality and consistency, thereby amplifying their impact and reshaping engineering organizations.
Key takeaway
For AI Architects and Directors of AI/ML navigating the integration of generative AI, recognize that your architectural judgment is now paramount. You must master a "second apprenticeship" in rule-setting and spec discipline to steer AI effectively. Failing to retool will lead to rapid codebase degradation and potential obsolescence, as AI automates junior-to-mid level coding. Focus on defining explicit rules for AI agents and using them to enforce quality, transforming your organization's output and cost structure.
Key insights
AI amplifies architectural judgment, making rule-driven specification critical for quality and rendering pure coding a commodity.
Principles
- AI generates "slop" at machine speed, compounding technical debt.
- Architectural judgment is tacit, built by varied, deliberate practice.
- Rules constrain AI, enabling quality at scale and consistent output.
Method
"Agentic Spec-Driven Development" involves defining precise rules and fences for AI, using silent coding runs to surface ambiguities, and generalizing fixes into new rules for consistent application across the codebase.
In practice
- Define explicit AI rules for interfaces and class creation.
- Use AI for silent runs to identify spec ambiguities.
- Generalize AI fixes into new, enforced rules.
Topics
- AI in Software Engineering
- Technical Debt
- Software Architecture
- Agentic Spec-Driven Development
- AI Code Generation
- Engineering Discipline
Best for: CTO, VP of Engineering/Data, AI Architect, Software Engineer, Director of AI/ML
Related on AIssential
See Counsel's argued verdicts on the open AI decisions leaders are weighing →
Editorial summary, takeaway, and curation by AIssential. Original article published by Towards AI - Medium.