Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
A precise name converts a fuzzy intuition into a findable, retrievable, composable object — and the act of naming changes what you can think.
Restructuring your notes restructures your understanding.
If capturing a thought takes more than a few seconds, you will not do it consistently — and inconsistent capture means permanent information loss.
Time your current capture workflow. Open a blank note on your phone or computer right now and start a stopwatch. Write a single sentence — any sentence. Stop the timer. If it took more than 5 seconds from intent to first keystroke, identify the friction: unlocking, finding the app, choosing a.
Building an elaborate capture system with tags, templates, and folder structures — then wondering why you never use it. The failure is optimizing for organization at the point of capture instead of optimizing for speed. Organization is a downstream activity. Capture is an upstream emergency.
If capturing a thought takes more than a few seconds, you will not do it consistently — and inconsistent capture means permanent information loss.
Record not just what you decided but why — because your future self will rewrite the reasoning after the fact, and you will never notice it happening.
Pick one decision you made in the past week — it doesn't have to be big. Write down: (1) what you decided, (2) the 2-3 reasons that drove the decision, (3) what you expected to happen, and (4) what alternatives you rejected and why. Time yourself. This should take under 5 minutes. If it takes.
Recording only the decision without the reasoning. A list of 'what I decided' is a changelog, not a decision journal. The value lives entirely in the 'why' — the assumptions, the constraints, the alternatives considered. Without that context, your future self has nothing to evaluate and nothing to.
Record not just what you decided but why — because your future self will rewrite the reasoning after the fact, and you will never notice it happening.
Observation and evaluation are neurologically distinct operations. Your brain can register what is happening before deciding whether it is good or bad — but only if you train the pause between the two. Collapsing them into a single act distorts perception and triggers defensive reactions in others.
Choose one domain you interact with daily — your calendar, your codebase, your team standup, your inbox. Instead of scanning for what is there, spend five minutes writing down what is absent. What meetings are not happening? What topics never come up? What people never speak? What errors are not.
Treating this as a philosophical curiosity rather than a diagnostic practice. You nod along — 'yes, blind spots exist' — and then return to scanning for what is present. The failure mode is agreement without application. You will know you have fallen into it when you cannot name a specific absence.
The most important information is often in what you habitually ignore.
In an information environment designed to overwhelm your cognition, the ability to detect signal is not an optimization — it is a survival skill that determines whether you act on reality or react to noise.
Your brain does not fail randomly. It fails in a specific, measurable, predictable direction: too much confidence. Across decades of research, in every population tested, the dominant calibration error is overconfidence — believing you know more than you do, that your estimates are more precise.
A log of predictions and outcomes shows you exactly where your perception is off.
An unwritten commitment is an invitation for your future self to renegotiate. Externalized commitments become binding infrastructure — visible, trackable, and resistant to the drift that lives between intention and action.
Assigning types to objects restricts what operations make sense on them.
Items that do not fit neatly into any category expose weaknesses in your system.
Choose a domain you organize — your notes, your project files, your reading list, your skill inventory. Pick five items and ask: does each item have exactly one parent, or does it genuinely belong in multiple categories? For each item with multiple natural parents, write down all the parents it.
Forcing lattice-shaped knowledge into tree-shaped containers. This happens constantly in practice. A team creates a folder structure for documentation and discovers that the "API Authentication" document belongs in both the "Security" folder and the "API Reference" folder. They pick one — say,.
Real knowledge often has items that belong to multiple parent categories. When you force every concept into a single branch of a tree, you destroy information. Lattice structures — where a node can have multiple parents — preserve the multidimensional nature of knowledge. The tree is a special.
Your risk model determines what you attempt and what you avoid.