Cognitive Debt

Hold

Techniques

A concept describing loss of shared understanding about a system among people.

Why it's here

Placed in Hold: 2 article(s) of evidence from 2 source(s), led by research-stage coverage, with 0 in the last 30 days. Confidence 44%.

3Simon Willison·7/2/2026research
Understand the code to work with coding agents
Simon Willison highlights Geoffrey Litt's talk on the need to understand code deeply when collaborating with coding agents. The main idea is that maintaining understanding helps avoid cognitive debt and allows developers to participate actively in the creative process as agents make larger changes.
4Martin Fowler·4/2/2026research
LLMs, cognitive debt, and verification in software development
Martin Fowler highlights a framework that separates system health into technical debt, cognitive debt, and intent debt, arguing that each limits a different aspect of software evolution. He also discusses research framing AI as a “System 3” in cognition, and notes that as coding agents reduce the cost of writing code, verification becomes the more valuable and difficult work.

Your vote is a weighted signal that nudges the radar — never a direct override.

HoldAssessConfidence33%

Business→ Steady
For BD, the impact is mostly indirect: as engineering teams need deeper code understanding to work with coding agents, response speed to customers and partners may depend more on internal coordination quality. BD will need to avoid overpromising delivery speed if the team is also dealing with added cognitive debt.
Developers✦ Emerging
As coding agents take on more code writing, understanding the code becomes part of day-to-day work rather than a nice-to-have skill. Developers will need to review agent-generated changes more carefully to avoid building up cognitive debt as the codebase becomes harder to follow.
Product→ Steady
With coding agents, PMs will need to pay more attention to coordination cost and shared product understanding, because the team depends more on knowing the code clearly to keep delivery moving. This does not change product goals, but it increases the importance of reducing ambiguity in requirements and changes.
Testers / QA✦ Emerging
As more code is produced by agents, testers will need to use their understanding of logic flow and code structure to design better tests, rather than only checking surface-level outputs. That raises the need to see through agent-generated changes and catch hidden defects earlier.

as of 7/3/2026

Educated guesses from the trend — you decide.