The earlier chapters of Part II asked what a developer must do when AI takes part in building and proving software. This chapter asks what that arrangement does to the developer. It treats the evidence on cognitive offloading, skill formation, complacency and overreliance among people who work with assistants, the experience of flow and craft when the typing goes, the identity of the person who chose the craft, and the ways developers keep their skill in practice. It concerns D3 Build and D4 Prove, because the skill at risk is the one that both functions depend on: the ability to read, debug and judge code that the developer did not type. The stewardship principle of Chapter 4 rests on it. A developer who cannot pass the tests Understand and Revert for a change cannot be its steward, and an oracle written by someone who no longer understands the system is not independent in any useful sense.
The chapter describes effects by population, task and result, says where a study is a preprint, a survey or a small experiment, and does not turn a finding about students or knowledge workers into a statement about developers in general. It ends with a practice plan and two worked examples.
Three earlier volumes treated the same question for other populations, and this chapter takes their conclusions as its starting point. AI Threat, Chapter 6, asked whether people are getting dumber and concluded that the evidence on offloading is conditional, and AI Threat, Chapter 14, treated skills and the ironies of automation, including the loss of the entry rungs by which experts are made (165, Nordqvist, 2026). AI Operations, Chapter 26, applied the argument to the operator's craft and concluded that skills are kept by working a protected share of cases without assistance, because supervision and the degraded mode after a stop need them (170, Nordqvist, 2026). AI Leader, Chapter 28, applied it to the leader's own mind, and its design response was a first view written before the briefing, a dark day with the assistants off and a named partner who reads a dated record (174, Nordqvist, 2026). The present chapter carries that design response over to the developer, with two differences. The developer's unaided skill is measurable in a way a leader's judgement is not, because code can be read, run and reverted. And the developer works with assistants and agents at higher degrees of delegation than most leaders do, so the offloading is more frequent and less visible.
Primary topics explored
- What this chapter builds on
- What studies measured
- Flow and craft
- Identity
- Stress, boredom and wellbeing
- Keeping skill in practice
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 28: The Developer's Own Mind: Craft, Flow, Cognitive Offloading and Identity in AI Developer gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “The Developer as a Person” and is one of 37 drawn from the manuscript.