Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
Regularly audit what you consume and cut sources that produce more noise than signal. Without scheduled review, your information environment silently degrades — and you adapt to the noise without noticing.
Sometimes you need the new schema to handle cases the old schema covered.
Identify one belief you've recently updated. Write down three situations where your old belief gave you a correct prediction. Now test: does your new belief also give correct predictions for those same situations? If not, your new schema isn't backwards compatible — it's just different, not.
Adopting a new mental model that explains the anomaly that triggered the change but quietly drops coverage of situations the old model handled well. You feel enlightened because you solved the puzzle that was bothering you, but you've introduced silent regressions — areas of life where your.
Sometimes you need the new schema to handle cases the old schema covered.
The faster you get feedback on an action the faster you can adjust.
Asking why five times in succession usually reaches the root cause of a problem.
Choose one recurring problem you have encountered at least three times in the past month — a meeting that always derails, a task you consistently procrastinate on, a tool that keeps breaking. Write the problem as a single factual sentence. Then ask 'Why does this happen?' and write the answer. Ask.
Stopping at the first answer that feels emotionally satisfying rather than continuing to the structural cause. The Five Whys fails most often not because people ask too few questions, but because the third or fourth answer lands on something that confirms an existing belief — 'the vendor is.
Asking why five times in succession usually reaches the root cause of a problem.
Too many agents create coordination overhead that can exceed their collective value.
Every pattern has a trigger — identifying the trigger is the key to changing the pattern.
Pick one pattern you want to change. Over the next three days, every time the behavior fires, immediately write down: (1) what time it is, (2) where you are, (3) who is around you, (4) what you were doing right before, (5) what emotion you were feeling. After three days, look at your logs. The.
Trying to change the behavior without identifying the trigger first. You white-knuckle through willpower for a week, then the trigger fires when you're tired and the pattern returns at full strength. The pattern isn't the enemy. The unidentified trigger is.
Every pattern has a trigger — identifying the trigger is the key to changing the pattern.
Run through scenarios mentally or in low-stakes situations before relying on a new agent.
A note that captures exactly one idea can be understood without its original context, linked to any argument, and recombined indefinitely — a note that captures two ideas can do none of these things reliably.
Open your notes app and find a note you wrote more than three months ago. Read it cold, as if someone else wrote it. Can you understand what it means, why you wrote it, and what you were supposed to do with it — without opening any other document? If not, rewrite it right now: add the source, the.
Treating context as overhead rather than structure. You tell yourself you'll 'remember what this means' or 'add context later.' You never do. Three months later, you've got a graveyard of orphaned fragments — technically captured, practically useless. The failure isn't that you took bad notes..
An atomic note should carry enough context to be understood without its original source.
When you trust your capture system your mind stops trying to hold everything.
An agent that fails to fire when it should leaves you exposed to undetected problems — the silence feels like safety, but it is blindness.
Record what you changed, why, and what happened — optimization without documentation is gambling.
Having more than one way to capture thoughts reduces the chance of losing important ones. A single capture tool creates a single point of failure in your thinking infrastructure.