The Future of the Developer: Fewer, More or Different?

All courses / AI Developer / Module 6 / Chapter 29

Learning objectives

After the lesson the participant can:

Classify statements about the future of the developer role as observable, expected or speculation
Compare the case for concern and the case for calm on the number of developers, and state what both accept
Explain the author's five projections and the threshold attached to each
Draft a horizon register with triggers that are observable in the organisation's own data

Key concepts

Horizon register: A list of trends, not a forecast. Each entry states the trend in one sentence, its label, the developer functions it concerns, the evidence and its age, the trigger that would change the label and the posture the organisation takes. It is kept as HZN in version control and approved by a decision record.
Three labels: Observable means happening now and documented in a cited source; expected means supported by a stated trend or a decided instrument; speculation means plausible and unevidenced. Most quantitative evidence is from the United States and from 2023 to 2026.
Agent-heavy team: A team in which a large share of changes is drafted by agents, with developers who frame, review and answer for them. Each stewardship test has a characteristic failure that more changes make more likely.
Projection with a threshold: Each of the author's five projections is paired with an observation that would make the author change it. The Level 4 prohibitions are not a projection: they are the ceiling the book recommends.
Different, with a qualification: The verdict's best single answer to the title: the work moves towards D1 Frame, D4 Prove and D5 Steward, and the entry route and the named steward are the two things an organisation can influence.

Interactive exercises

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

Interactive exercise 1 · Sort

Observable, expected or speculation

Sort each statement about the future of the developer role under the label the chapter gives it.

Interactive exercise 2 · Put in order

Keeping a horizon register

Put the steps of the practical guide for a horizon register in order.

Teaching plan

10 min	The teacher collects predictions about developers from the room and has participants label each as observable, expected or speculation.
15 min	Lecture on what the employment data show and do not show, on agent-heavy teams and on the specification as the main artefact.
15 min	Staged debate in four steps on fewer, more or different, ending with the verdict and the five projections with their thresholds.
25 min	Exercise: groups write a horizon register of four or five trends for their organisation.
10 min	Groups exchange registers and test whether each trigger could actually be observed in the organisation's own data.

Discussion

The concerned side treats the entry-level data as the earliest signal of a larger change, the calm side as a hiring cycle that predated the technology. What observation would move you from one reading to the other?
Projection P5 says the named steward persists because the law names a party. Which of the book's arguments would have to fail for that to be wrong?
Nordvik Region's concern is the number of juniors it can afford to place, Hansa Mutual's the number of maintainers who will be gone. What is the equivalent entry in your own register?

Written exercise

Exercise · 25 minutes

A horizon register for developer roles

Write a horizon register for developer roles in your organisation, or for Hansa Mutual. Choose four or five trends that matter, for example the entry route, agent-authored change, the specification as reviewed artefact, the retirement of legacy maintainers and a dated legal duty. For each, write the trend in one sentence, its label, the developer functions it concerns and the evidence with its age in months. State the scope limit of the evidence: country, period and occupation. Write the trigger as an event observable in the organisation's own data, the posture taken now, the owner and the review date. Require the register before any headcount decision that cites AI.

Deliverable: A horizon register of four or five labelled trends with evidence age, scope limit, trigger, posture, owner and review date.

Your work

Self-test

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

How does the verdict label the statement that total employment in software roles in the EU holds to 2036, with a shift in the content of the work?
Show the answer
C. Expected
The summary lists it under expected. Lower employment of the youngest workers in exposed occupations in the United States is observable, and the size of a development organisation in 2036 is speculation.
Which projection does the author label as speculation?
Show the answer
B. P3: a few named stewards answer for many agent-authored changes in some units
P1, P2 and P5 are labelled expected. P3, on a small number of stewards for many agent-authored changes, and P4, on specifications and oracles as the primary reviewed artefacts, are labelled speculation.
What does the chapter say about the Level 4 prohibitions in relation to the projections?
Show the answer
D. They are not a projection but the ceiling the book recommends
The chapter states that the prohibitions are not a projection, and that no threshold above would lift them without a change in what can be verified and stopped from outside the system.