Document what you have learned to ignore — not just what you prioritize — as expertise develops
During expertise development, explicitly document both what you now prioritize and what you have learned to ignore, as conscious articulation of ignored features is the operational test of signal efficiency.
Why This Is a Rule
Expertise is as much about what you've learned to ignore as what you've learned to see. A novice programmer notices every line of code equally. An expert's eyes skip boilerplate, configuration, and standard patterns to lock onto the unusual — the subtle bug, the unexpected dependency, the non-obvious design choice. This selective attention is the core mechanism of expert performance.
But the "learned to ignore" list is usually tacit — experts can demonstrate it but not articulate it. Making it explicit produces two benefits. First, it's transferable: you can teach others not just what to look for, but what to stop looking at — which accelerates their development. Second, it's auditable: you can check whether what you're ignoring is still safely ignorable. Expert blind spots form when conditions change but the "ignore" list doesn't update — the thing you correctly ignored for five years became important last month, but your attention filter still skips it.
When This Fires
- During periodic reflection on your developing expertise in any domain
- When mentoring someone and trying to accelerate their signal-noise discrimination
- After a mistake that resulted from ignoring something that turned out to matter
- Any expertise development context where you want to make implicit filters explicit
Common Failure Mode
Documenting only what you prioritize: "I look for error handling, edge cases, and naming consistency in code reviews." This is half the picture. The other half: "I've learned to ignore: standard library usage patterns, formatting that matches our linter, import organization, and test setup boilerplate." The ignore list is where expert efficiency lives — and where expert blind spots hide.
The Protocol
Periodically during expertise development: (1) Write: "In [domain], I now prioritize: [list 5-7 high-signal features]." (2) Write: "In [domain], I have learned to safely ignore: [list 5-7 features I skip over]." (3) For each ignored feature, verify: "Is this still safe to ignore? Have conditions changed?" (4) The ignore list should grow as expertise deepens — if it doesn't, you're still processing noise that experts would skip. The priority list should sharpen — if it doesn't, your signal detection isn't improving.