The new hire shipped in week one. What did they learn?
Researchers named the failure mode: metacognitive laziness.
- The track
- Leads a team
- The rep
- About thirty seconds
- Published
- September 2, 2026
The Exhibit
A new hire merging a real PR in their first week feels like a fast, healthy onboarding. It may be measuring the tool, not the hire. Peer-reviewed work coined the term "metacognitive laziness" for the pattern: leaning on AI lets people produce correct-looking work while skipping the deeper processing that learning actually requires. The study.
Shipping and understanding used to travel together for a new hire, because you could not ship what you had not figured out. AI uncoupled them. Now someone can clear the ticket without building the map of the system, and the merged PR will not tell you which one happened.
The study
Comprehension Debt
Comprehension debt: the gap between what gets shipped and what the team can still reason about.
For onboarding, that gap is the risk that matters. The first ninety days are when someone builds the mental model they will rely on for years, and it is the cheapest depth you will ever add to the team. A fast first PR can buy you a hire who never gets past week one, which is a re-hire you pay for later. So measure the model, not the merge. A short walk-through of why they made a choice tells you more about how onboarding is going than the throughput chart ever will, and it tells you while you can still do something about it.
The idea
The Rep
One for your next review:
A new engineer's endpoint works and passes review. In production it is fine for a 10-item list and times out on a 500-item one. The code reads cleanly: for each item, look up its author by id.
How onboarding is really going shows up in two questions: can anyone name the N+1 pattern, and does anyone notice that "reads cleanly" and "falls over at 500 rows" are both true at once? The loop firing one query per item is the thing to spot. If clean-and-green counts as finished, the gap is in the onboarding, not the new hire, and you can close it now with a walk-through instead of later with a postmortem. Clean code that is correct on small inputs is just what someone ships when they know the language but not yet the system.
About thirty seconds