Describe a familiar system for 10 minutes without…
When encountering a familiar system or codebase, force yourself to describe what you observe using only concrete sensory details for 10 minutes before applying any evaluative categorization or pattern labels.
When This Fires
- Returning to a codebase you haven't touched in months
- Reviewing a system you originally designed (where your mental model is strongest and most outdated)
- Starting a debugging session in familiar code
- Any time you feel you already know what you'll find before looking
Common Failure Mode
Describing for 2 minutes, getting bored because "I know this system," and switching to evaluation mode. The 10-minute constraint is the point — the first 2-3 minutes produce descriptions that match your existing model. Minutes 4-10 are where you start noticing things that don't match. The boredom is a signal that your expert categories want to take over. Push through it.
The Protocol
Set a 10-minute timer. Open the system/codebase. Write only concrete descriptions: file names, function signatures, data flows, dependency counts, error handling patterns. No adjectives (good, bad, clean, messy). No pattern labels (MVC, microservices, monolith). No evaluations (over-engineered, under-tested). After 10 minutes, read your descriptions and ask: "What surprised me?" The surprises are where your mental model had silently diverged from reality.