Cognitive Debt in the GenAI Era: Listening to Practitioners' Voices on the Loss of Understanding · Theocharis Tavantzis (Aalborg University) and eight co-authors, including Margaret-Anne Storey (University of Victoria) · arXiv preprint
A review of 76 practitioner sources catalogs how teams try to prevent and detect lost understanding of AI-written code
Machine-readable
Download Markdown
The authors reviewed sources published from February 2025 to September 2026: 58 practitioner articles, 11 company or vendor articles, five arXiv preprints, one industry report and one technical document. No forum threads passed their quality filter. They define cognitive debt as the accumulated gap between the understanding a team has and the understanding it needs for current or future work. Their finding is that it can build up unnoticed behind working code and passing tests when developers accept AI-generated solutions without building understanding.
The preventive practices practitioners propose include comprehension gates, review-sized changes, externalizing intent and executable guardrails. Proposed signals include reliability metrics and cognitive-debt audits.
This is a synthesis of what people wrote, not a measurement. The authors say they do not estimate prevalence and did not compute inter-coder agreement, and they used Claude Fable 5.1 for part of the source search. We read the abstract, the method and the opening of the results, not the full results.
Why it matters: It is a list of what other teams report trying, which is useful if your agents merge changes faster than anyone reviews them. Because it counts what practitioners wrote and not what worked, treat each practice as a candidate to test.