AI & Software EngineeringKnowledge Atlas
Catalogues / NDSE2 chapter guides and sources

C:C10

Chapter 10: Developer Learning, Mentoring and Comprehension Debt

A guide to the published second edition, with literal citations separated from wider editorial reading suggestions.

Open this group in the atlasChapter catalogue entry

Chapter guide

Distinguishes assisted task completion from retained competence. Mentoring, explanations, repairs and deliberate practice lead to delayed retention and transfer checks; proposed competence measures remain instruments to validate rather than established scores.

Apprendimento, mentoring e debito di comprensione degli sviluppatori

Sintesi in italiano

Distingue il completamento assistito di un compito dalla competenza conservata. Mentoring, spiegazioni, correzioni e pratica deliberata conducono a verifiche differite di ritenzione e trasferimento; le misure di competenza proposte restano strumenti da validare.

Learning goals

  • distinguish finishing a task from learning to maintain it
  • design delayed retention and transfer checks
  • give junior developers meaningful responsibility without treating unvalidated competence scores as established measures
Obiettivi in italiano

Obiettivi di apprendimento

  • distinguere il completamento di un task dall'apprendimento necessario per mantenerlo
  • progettare verifiche differite della retention e del transfer
  • assegnare responsabilità significative agli sviluppatori junior senza presentare punteggi di competenza non validati come misure consolidate
Chapter outline
  • 10.1 Short-term task success versus retained understanding
  • 10.2 Comprehension debt is distinct from technical debt
  • 10.3 Novices, misconceptions and verification difficulty
  • 10.4 Cognitive offloading, physiology and limitations
  • 10.5 Learning through explanations, repairs and code tours
  • 10.6 Onboarding is a long process, not a first PR
  • 10.7 Mentoring and apprenticeship in a team with agents
  • 10.8 Measuring retention and engineering fluency
  • 10.9 A practical capability-development contract
  • 10.10 Worked engineering example: measure what the engineer remembers
  • 10.11 Practice exercise: test whether competence survives the assistant
Struttura del capitolo
  • 10.1 Completare un task non significa conservarne la comprensione
  • 10.2 Il debito di comprensione è diverso dal debito tecnico
  • 10.3 Principianti, fraintendimenti e difficoltà di verifica
  • 10.4 Cognitive offloading, fisiologia e limiti
  • 10.5 Imparare attraverso spiegazioni, correzioni e code tour
  • 10.6 Onboarding: un percorso, non la prima PR
  • 10.7 Mentoring e apprendistato in un team con agent
  • 10.8 Misurare retention e padronanza ingegneristica
  • 10.9 Un contratto pratico per lo sviluppo delle competenze
  • 10.10 Esempio svolto: misurare ciò che l'ingegnere ricorda
  • 10.11 Esercizio: verifica se la competenza rimane quando l'assistente non c'è

Cited in the published chapter

23 linked atlas references from literal citations in the English and Italian editions. General bibliography membership and identifier-index entries are counted separately.

SE@PoliMi bibliography 18

Addy Osmani 2

The Pragmatic Engineer 1

Martin Fowler’s website 1

Book and contextual references

Trace literal citations to chapter sections

Locations come from the supplied English and Italian source files. Chapter text and figure captions are identified separately; identifier-index references and general bibliography membership are not treated as chapter citations.

Complete citation locators and source hashes

Editorial reading mappings

Broader topical suggestions can overlap the cited sources. A mapping does not add a citation to the published edition or establish that a practice is effective.

SE@PoliMi bibliography 63

Addy Osmani 7

The Pragmatic Engineer 16

Martin Fowler’s website 12

Earlier Non-Deterministic books 12

Software Engineering Practices 4