Treat a newcomer's unanswerable question as a signal…
When a newcomer to a codebase or system asks a question you cannot immediately answer about code you wrote, treat their question as a defamiliarization signal requiring investigation rather than dismissing it as lack of context.
When This Fires
- During onboarding walkthroughs when a new team member asks about your code
- In code review when a less experienced reviewer flags something you consider obvious
- When someone from another team questions a design decision you've long taken for granted
- Any time your response to a question is "well, it's complicated" or "there's a lot of history there"
Common Failure Mode
Explaining the history instead of investigating the question. "Oh, that's because two years ago we had to support both APIs during the migration and we just never cleaned it up." The explanation satisfies the newcomer — they nod and move on. But the explanation revealed that your code contains migration debt you'd forgotten about. The newcomer's question was an opportunity to fix something; the history lesson was a way to avoid the fix.
The Protocol
When a newcomer asks a question about your code that you can't immediately answer clearly: (1) Resist the urge to explain or contextualize. (2) Write down the question exactly as asked. (3) Investigate it as if you didn't write the code. (4) If the investigation reveals something that should be documented, simplified, or fixed — do it. The newcomer just performed free defamiliarization on your codebase. Honor it with action, not history lessons.