Every profession has a lowest rung where the work is easy enough to be done by someone who does not yet know the profession, and useful enough that doing it teaches the profession. This chapter asks what happens to that rung in software development when an assistant writes the small function, drafts the test and explains the unfamiliar module. It concerns D3 Build, because the tasks at issue are the making of code, and D4 Prove, because the skill that a junior most needs to acquire, and that the organisation most needs to be able to rely on, is the ability to judge whether a change is right. It is a debate chapter: it asks whether junior developers will disappear, states the case for concern and the case for calm at their strongest, and ends with a verdict and an artefact, the apprenticeship plan APR-*, that a tech lead and an engineering manager can put in version control on Monday.
The chapter builds on conclusions the earlier volumes reached for other roles. Architecture as Code (Chapter 18) managed competence as a skills matrix in a loop of assessment, planning, learning, application and measurement (161, Nordqvist, 2025). AI Governance, Chapter 14, assessed competence by practical demonstration and treated assessment results as personal data whose use is agreed with employee representatives (162, Nordqvist, 2026). AI Threat, Chapters 7 and 14, collected the evidence that learning without struggle weakens learning (165, Nordqvist, 2026). The Transformed Security Architect, Chapter 15, made keeping the craft a design decision (166, Nordqvist, 2026); AI Blue, Chapter 23, named the two halves of the apprenticeship problem (168, Nordqvist, 2026); AI Purple, Chapter 24, found the evidence on skill beside automation dependent on how the assistant is used (169, Nordqvist, 2026); AI Operations, Chapter 26, held that a thinning supply of entry-level operators is expected where organisations let it and that wholesale loss of the craft is speculation (170, Nordqvist, 2026); and AI Leader, Chapter 11, carried the problem to leadership (174, Nordqvist, 2026). This chapter takes the developer form, which the series states as open question Q19: where the next senior developers come from if the tasks that taught the craft are the tasks AI performs best.
Chapter 2 described what developers did before AI. The part of that description that matters here is how the craft was passed on. The account below is the book's own analysis, offered as a checklist and not as a finding from a study of how developers are made; the studies cited later in the chapter measure other things.
Primary topics explored
- How juniors learned
- What AI changes
- What studies measured
- The debate
- Verdict
- Designing the apprenticeship
About AI Developer
AI Developer is Book 12 of The Transformed Architecture. It takes the developer as its subject and asks what happens when AI is used broadly in software development: the five developer functions (frame, design, build, prove, steward), the delegation ladder and the Level 4 prohibitions, the stewardship principle (name, understand, revert), verification as the scarce skill, the junior pipeline, adoption and productivity as claims that need evidence, regulation (the AI Act, the Cyber Resilience Act, the Product Liability Directive, NIS 2, DORA, the GDPR), ethics, intellectual property and sovereignty in the toolchain, and the developer as a person, for European enterprises and public authorities.
It builds on the conclusions of Architecture as Code, AI Governance, AI Platform and Security, AI Red Team, AI Threat, The Transformed Security Architect, AI Boss, AI Blue, AI Purple, AI Operations and AI Leader.
developers at every level, tech leads and engineering managers, architects, platform engineers, site reliability engineers and testers, product owners and designers, leaders who decide on developer tooling, heads of public-sector IT and procurement, works councils and unions, educators, and supervisors and auditors.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Chapter 13: The Junior Developer and the Apprenticeship Problem in AI Developer gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Developer Roles Across the Organisation” and is one of 37 drawn from the manuscript.