The Junior Developer and the Apprenticeship Problem

All courses / AI Developer / Module 3 / Chapter 13

Learning objectives

After the lesson the participant can:

• Explain how the entry tasks of a junior developer separated into an output a tool can supply and a learning it cannot
• Compare what the studies of early-career employment, novice productivity and learning beside an assistant each measured
• Compare the case for concern and the case for calm, and state the points on which they meet
• Design a first-year apprenticeship plan with milestones, tool access by phase and an AI-off share

Key concepts

The apprenticeship problem

The separation of output from learning. A task has an output, which the tool can now supply, and a learning, which the tool supplies only if the junior does the thinking the tool is replacing. The question is where the next senior developers come from.

Attempt first

The junior states what the problem is, what a solution would look like and where in the code it would go, before opening the assistant's draft, and keeps a short log of what the assistant got wrong.

Review first

The junior becomes a reader before a writer by reviewing pull requests as practice. One rule protects the design: the junior's review is practice, not the gate, and it does not count as an approval.

AI-off practice

Tasks done without any assistant, including ambient completion, for a stated time. The plan fixes the share and its reason, and the platform team configures the tools so that completion can be switched off for a named learning period.

Apprenticeship plan

The artefact APR: a first-year route with a named plan, mentor and second assessor, four to six milestones, tool access that starts below the team ceiling and rises, and evidence from work and not from telemetry. No assistant assesses a named junior.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Teaching plan

Discussion

1. The chapter says the decline in hiring is a choice, not a law. Who in your organisation makes that choice, and on what figure?
2. A broker interface team at Hansa Mutual took no apprentices for 2030 on the strength of a figure of 42 per cent AI-assisted lines. What would the claim record of Chapter 4 have required before that decision?
3. Skill is the measure, not output. How would you know after one year that a junior can own a change, without using telemetry about that person?

Written exercise

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

1. What did the study by Humlum and Vestergaard, linking chatbot adoption surveys to Danish administrative records, find?

   1. Precise null effects on earnings and recorded hours two years after the launch
   2. A fall of about a fifth in the employment of the youngest workers in exposed occupations
   3. A 26.08 per cent increase in completed tasks, larger for less experienced workers
   4. A lower score on a comprehension quiz for participants who used an assistant
   Show the answer

   A. Precise null effects on earnings and recorded hours two years after the launch
   The chapter cites it as the study that points the other way from the American payroll data: no measurable effect on earnings or hours in Danish records, which is why the evidence is called young and conditional.

2. Which rule does the chapter set for the junior's review of pull requests?

   1. It counts as one of the two required approvals once the mentor has signed it
   2. It replaces the senior's review for changes outside security-critical paths
   3. It is practice and not the gate, and it does not count as a required approval
   4. It is done only with the AI reviewer's comments visible, to save time
   Show the answer

   C. It is practice and not the gate, and it does not count as a required approval
   Review-first learning turns the junior into a reader before a writer, and one rule protects it: the junior's review is practice and not the gate through which the change passes.

3. How does the verdict label the claim that the junior developer will disappear?

   1. Observable, on the strength of the American payroll data
   2. Expected, because the entry tasks are already delegated
   3. Refuted, because every earlier wave of tools kept juniors
   4. Speculation, since no evidence cited supports the claim
   Show the answer

   D. Speculation, since no evidence cited supports the claim
   The verdict calls lower hiring in some datasets observable, a thin supply of developers able to supervise generated code expected where no route is designed, and the disappearance of the junior speculation.