← Golden path01 / THINK
How a thing
is reasoned about
The path to a conclusion, kept rather than the conclusion alone. What was read, where it was wrong, what changed.
01
How does he reason?
The path to a conclusion, kept rather than the conclusion alone. What was read, where it was wrong, what changed.
Most of the case studies were meCharlie Munger recommended it, so I finally read it. Checking the principles one by one, I found I was not the one reading the case studies — I was inside them.~4 minThere was no need to cut the release branch late"It worked in QA but broke on deploy" is not an accident once it repeats. The combination verified is not the combination shipped.~9 minThe bugs the gates let throughSix checks all green while the share-card image vanished and the home headline was invisible. The gates were not wrong.~6 minHow to read mathematical statistics notationFifty symbols with how to say them out loud. A formula does not fail because the idea is unknown — it fails because the symbols cannot be spoken.~4 minThe sidebar vanished on exactly one screenFive hypotheses, all disproved, and only then the cause. CSS specificity colliding with route chunk load order.~4 minA check that never fails is not a checkEvery guard gets deliberately broken. A guard confirmed only by passing guarantees nothing.~1 minThe colour was calculated, not chosenInstead of picking the accent by eye, it was worked backwards from a contrast target — and the constraint became the art direction itself.~2 minA personal wiki an LLM reads as a primary sourceWhat changes when a wiki is built for an LLM to read rather than for a person. The procedure, written so it reproduces from zero.~6 min