Conclusion: The Developer with AI Judged

All courses / AI Developer / Module 7 / Chapter 33

Learning objectives

After the lesson the participant can:

• Explain the verdict on each of the five parts of the thesis and the thinnest point of each
• Classify a claim of the book as established, expected or speculation, using the chapter's meaning of established
• Review where the book's evidence is thin and what would show the thesis wrong
• Apply the five Monday actions to one's own organisation and record the results in a scorecard

Key concepts

Established

Used in this chapter only for what is both observable and in force. The book's own conventions, such as the 90-day and 180-day evidence clocks, the starting levels, the review budget and the AI-off share, are design choices and not findings.

Verdicts part by part

Part 1 is expected in direction and speculation in pace. Part 2 is firm where law and documented failure make it firm and recommended elsewhere. Part 3 is conditional. Part 4 is strongest as a design principle. Part 5 holds, because it can be checked against an organisation's own records.

Stronger on records than on outcomes

The thesis is stronger where it asks for records and weaker where it predicts outcomes. The chapter lists ten places where the book found no study, including a designed apprenticeship, review under volume and the developer's own skill over years.

What would show the thesis wrong

Independent multi-year evidence of better outcomes without named owners and independent checks, or evidence that developers who never write or read code by hand verify as well as those who do. Nothing found meets either bar, which the chapter calls a weak form of support.

Thesis scorecard

A record in version control that gathers the verdicts with the age of each piece of evidence. A claim past its expiry is marked expired and not removed, and the field that counts refutation tests seen is zero.

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 thesis has not been refuted, and the chapter says it could not have been by the evidence gathered. How much weight should a design principle carry when its outcomes are untested?
2. A critic could say that few developers ever passed Understand for a legacy module without the colleague who wrote it. How would you answer that challenge?
3. Part 5 can be checked in an afternoon against an organisation's own records. What would such an afternoon find in yours?

Written exercise

Self-test

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

1. What verdict does the chapter give on Part 3 of the thesis, that verification becomes the scarce skill and the junior pipeline must be rebuilt?

   1. It holds without qualification, because several long-term studies confirm it
   2. Conditional: pressure on the entry route is observable, the remedy untested
   3. It is refuted by the field experiments that found productivity gains
   4. It is speculation in every respect and should be dropped from planning
   Show the answer

   B. Conditional: pressure on the entry route is observable, the remedy untested
   The chapter calls this the part with the most inference between evidence and claim. The pressure on the route is observable, the case for a designed route stands, and no study of a designed apprenticeship was found.

2. Which part of the thesis does the chapter say has the most direct support, and why?

   1. Part 1, because employment data for Europe confirm the transformation
   2. Part 2, because benchmarks show agents fail above Level 3
   3. Part 4, because courts have already applied the three tests
   4. Part 5, because it is partly a method and can be checked against an organisation's own records
   Show the answer

   D. Part 5, because it is partly a method and can be checked against an organisation's own records
   Claims with evidence holds because it is partly a method: gaps between perceived and measured effects and between dashboards and samples are documented, and it can be checked in an afternoon.

3. Where does the author's projection Q3 expect the ladder to be raised first?

   1. At Level 3 Bounded, in mechanical, reversible classes such as dependency patches
   2. At Level 4 Autonomous, for security-critical code once models improve on the benchmarks
   3. At Level 2 Supervised, for decisions about named developers
   4. Nowhere, because the ceilings are fixed by law for all classes
   Show the answer

   A. At Level 3 Bounded, in mechanical, reversible classes such as dependency patches
   Q3, labelled expected, names Level 3 Bounded in classes such as dependency patches, formatting, generated documentation and test-data maintenance, each with a gate the change cannot alter.