‹

Training the Edge

EN

Training the Edge

Part IV ended with a claim that should sound suspicious: the human edges that hold — calibration, continual learning, efficient acquisition, taste, ownership — are exactly the ones a person can train. Suspicious, because "you can train it" is where thinking books traditionally start lying. Training advice is the one corner of this genre where wishful thinking turns a profit.

So this chapter carries the heaviest density of claim grades in the book. What follows is not a philosophy of self-improvement. It is a short list of practices with evidence behind them, a pointer to the famous practices with autopsies behind them, and a protocol for using a machine as a sparring partner without letting it become a crutch. Chapter 16 turns all of it into a schedule.

The gym that does not work

Begin with the graveyard's freshest stone.

The pitch is familiar: ten minutes of app puzzles a day, and memory, attention, and general intelligence rise like a trained muscle. The pitch was tested properly, once, at scale. In 2010 Adrian Owen and colleagues ran 11,430 adults through six weeks of online brain training and measured what moved (Nature, 2010). Scores on the trained tasks climbed steeply. Scores on everything else — including untrained tasks that were close cousins of the trained ones — did not move ⚖. A 2016 review by Daniel Simons and six colleagues read the industry's entire evidence file and reached the same verdict: strong evidence of improvement on the practiced games, little for near transfer, none convincing for "your life improves" ⚖. The same year, the US Federal Trade Commission fined Lumosity's maker two million dollars for deceptive advertising. The full autopsy — with five sibling myths in adjoining plots — is in Appendix B ⚠.

Why it fails is a mechanism worth owning ⚙: practice is brutally specific. You improve at what you literally do, plus a thin ring of neighbors. The classic demonstration is fifty years old. Chess masters can glance at a mid-game position and reproduce it almost perfectly; club players cannot. Scramble the same pieces into random nonsense and the masters' superpower evaporates (Chase and Simon, 1973 ⚖). The masters never had better memory. They had a library of chunks, and random boards contain no chunks. The skill was never general; it only looked general from outside.

And here is the corollary this book cannot dodge: puzzles obey the same physics. Solve the fifty in this canon carelessly and the main thing you will get better at is those fifty puzzles. A puzzle book that promises more, with no mechanism, is a brain-training app with better typography.

This book was built around the escape clause.

The escape clause: name the move

The escape clause has an experimental pedigree. In 1980 Mary Gick and Keith Holyoak gave people Duncker's radiation problem — destroy a tumor with rays that wreck healthy tissue at full strength — after having them read a military story with the identical skeleton: a general splits his army into small columns that converge on a fortress from all sides. About one solver in ten cracks the tumor unaided. Having just read the fortress story, still only about three in ten make the leap on their own — the analogy sits in memory, inert. Told "that story you read may help," most solve it at once ⚖. The knowledge was there. The recognition wasn't. In the follow-up work, one group transferred spontaneously at much higher rates: people who had read two analogous stories and written down the skeleton the stories shared ⚖.

That is this book's whole theory, in one experiment ⚙. Transfer follows the named, compared schema — not the exposure. Solving the two-ropes puzzle teaches you the two-ropes puzzle. Solving it and then writing "the move was exploit rates, not lengths — find the quantity the mess can't touch" files something reusable. A move you can name is a move you can notice, and noticing is the entire game. Part III made the argument in full: expertise is a library of recognition-action pairs, compiled from solved and failed problems, converting search into lookup. A medalist carries perhaps two hundred. This book issues thirty-two — Appendix A — and the difference between reading them and owning them is the training below.

What transfers, then, is move-recognition across varied surfaces ⚖ — and it transfers under known, unglamorous conditions that half a century of memory research keeps re-confirming:

PrincipleWhat it means hereGrade
Retrieval beats re-readingRe-solve from the bare statement; don't reread solutions and nod along⚖ Roediger & Karpicke, 2006
Spacing beats massingReturn after days and weeks, not minutes⚖ Cepeda et al., 2006
Variation beats repetitionSame move, different costume, on purpose⚖ interleaving literature
Difficulty is a featureEffortful, error-prone practice outlearns smooth practice⚖ Bjork's "desirable difficulties"
Fluency is a liar"That felt easy" measures familiarity, not learning⚖

The last row is the dangerous one. The practice that feels productive — rereading elegant solutions, watching someone else be clever — produces fluency, and fluency feels exactly like skill from the inside. The practice that works feels worse while it works. Plan for that, or the plan fails.

The instruments

Competitive mathematics and competitive programming form the most refined training culture our species has built for reasoning — unusually honest because its feedback is unfakeable: the proof works or it doesn't; the code passes or it doesn't. Chapter 8 described that culture from the inside. Here are its instruments, domesticated for a civilian with half an hour a day.

Upsolve

The problems you fail are the syllabus. The culture's single most agreed-upon practice: after any session, go back to what beat you — the same day, before the sting fades — and solve it properly. A problem is owned when it has been re-solved from a blank page, not when its solution has been read and understood. Understanding someone else's solution is a spectator sport ✦. Competitors say a problem has "entered the hands" only after the re-solve, and the phrase is exact: the hands, not the head.

The mistake journal

The non-negotiable instrument. Every miss becomes an entry, and every entry names the move that was missed, using the index's vocabulary. Five lines:

  1. Date, and the puzzle (by chapter·number).
  2. Where I stalled — one sentence.
  3. The move I missed — by name, from Appendix A.
  4. The recognition signal I ignored — one sentence.
  5. The class of miss: misread · wrong frame · right move, too late · unproven leap · bookkeeping.

The classification line looks bureaucratic and is the most valuable line. "I am bad at puzzles" is a mood; "three of my last five misses were unproven leaps" is a diagnosis with a prescription attached — Chapter 10's exchange-argument discipline, applied until the leak closes. High-rated competitors keep exactly this ledger over years of contests; the journal is their error distribution made visible, and then made smaller.

Spaced review — of misses only

Re-solving your victories flatters; re-solving your failures teaches. The journal doubles as a review deck: each missed puzzle comes back at roughly three days, two weeks, and two months — re-solved cold, from the statement, with the re-solve time logged. Misses only. The wins need no rehearsal, and rehearsing them is how practice time quietly becomes entertainment ✦. This is spaced repetition, the most robust result in the learning literature ⚖, pointed at reasoning patterns instead of vocabulary — a personalized curriculum in which every card earned its place by beating you.

The ladder: one star up

Comfort teaches nothing; panic teaches nothing. Competitive programmers phrase it as the +200 rule — practice about two hundred rating points above yourself. Here the unit is stars: work one star above the level you can solve cleanly. The signals are symmetrical. Weeks with an empty journal mean the ladder is too low; sessions that are all hints and no motion mean it is too high. Hard enough to hurt, close enough to finish.

Struggle before solutions

Thirty minutes of genuine motion before reading any solution — and motion has a definition: representations tried, cases enumerated, small instances computed. Rereading the statement and hoping is not motion. After thirty minutes, take one hint's worth — a sentence, a nudge, never the walkthrough — and dive again. Reading solutions early trains a real skill: recognizing solutions. It is the wrong skill ✦. This is also why every solution in this book sits behind a pause line. The pause line is the pedagogy.

Check by a second road

Borrowed from engineers, who call it stress-testing and run it mechanically: when a contest solution looks right, they write a dumb brute-force twin and diff the two until a counterexample appears or confidence is earned. The civilian version costs two minutes: before declaring victory, ask what independent computation would agree with me if I'm right? Part III held itself to that standard — the circle-regions formula derived incrementally and then re-derived through Euler's formula; the twelve-coin scheme checked against its information budget. One road is an opinion. Two roads that meet are a result ✦.

Calibration: practicing "I don't know"

Chapter 13 argued that knowing-what-you-don't-know is among the most durable human edges — and showed what its absence costs in fabricated citations and vaporized careers. The good news is that no moat in that chapter is cheaper to train. The instrument is a pencil.

The protocol: once a week, five questions. For each, build a Fermi chain — decompose, estimate, multiply, the move of 6·46 — and commit to a point estimate plus an 80% interval: "I am 80% sure the true number lies between these bounds." Then check, score the hits, and plot the running hit rate. The target is not narrow intervals. The target is honest ones: intervals labeled 80% that capture the truth 80% of the time. Widening your intervals until they stop lying is progress, however deflating it feels ✦.

Expect a rough start. In the classic experiments, people's "98% confident" intervals contained the truth roughly 60% of the time (Alpert and Raiffa's subjects, replicated for decades ⚖). Overconfidence is the human default, not a character flaw — which is exactly why a logged curve beats a self-image. Question sources are everywhere: world numbers (a country's population, a river's length), personal numbers (unread emails, steps to the station), and this book's own numbers before you check them — how many arrangements of the 15 puzzle are reachable? Monty Hall belongs in this section for one reason: 6·33 is the canon's standing proof that confidence and correctness are different axes, even — especially — for experts. Ten thousand letters said so.

Two habits extend the log. First, tag everything: before checking any solution, write a percentage next to it. The habit generalizes far beyond puzzles, and it is the same habit this book's claim grades perform in print — ⚖ versus ✦ is a confidence interval wearing typography ⚙. Second, grade your sources the same way, including the machine ones. That becomes load-bearing two sections from now.

Insight hygiene

Insight resists scheduling, but it has hygiene — conditions under which the restructuring of Chapter 4 happens more often. Two are evidence-backed; one is a drill.

Incubation is real, and modest ⚖. The meta-analysis of a hundred years of incubation experiments (Sio and Ormerod, 2009) finds genuine but small effects, strongest when the impasse was honestly earned and the break is filled with something light — a walk, a chore — rather than more grinding or a second hard problem. The mechanism constraint matters ⚙: incubation consolidates work already done. Parking an unexamined problem parks nothing.

Sleep helps more ⚖. In the Nature experiment that made the point stick (Wagner et al., 2004), solvers practiced a number task containing a hidden shortcut; after a night's sleep they were more than twice as likely to discover the shortcut as those who stayed awake the same interval. The protocol writes itself: struggle fully, write down the exact stuck-point in one sentence — the writing is the loading step — park it overnight, keep paper within reach. The shower is not magic. The loaded question is ⚙.

The drill: question the constraints. The trainable half of insight is not waiting for restructuring — it is hunting the restructure on paper. Stuck for ten minutes? Write every rule you are obeying. Mark each one STATED or ASSUMED. Attack the oldest ASSUMED first. This is 4·11's move run as a checklist, and 4·13's lesson made procedural: the boundary that blocks you was never in the statement. The object-form of the same drill comes from 4·14: for each thing in the problem, ask what else is this, ignoring its label? Three minutes, in writing, every time. Insight as checklist is less romantic than insight as lightning, and considerably more available ✦.

The sparring partner

As of July 2026, a frontier AI model will solve most of the classics in this canon on sight — they are in its training data — and will produce fluent, confident solutions to fresh puzzles that are usually right and occasionally, with identical confidence, wrong ⚖. That combination makes it the best sparring partner ever built and the worst possible answer key. Three uses and one prohibition.

Generate variants. Ask for the same move in a new costume: "Here is a puzzle and the move it teaches [statement, plus the move's name]. Write three new puzzles that use the same move with entirely different surfaces — no ropes, no burning. Do not include solutions." This attacks surface-binding, the failure mode the brain-training industry never solved, and it is Gick and Holyoak's compare-two-analogs condition, industrialized: the machine varies the costume, you extract the skeleton. Machines are excellent at costume.

Verify after committing. Solve first. Write your answer and your confidence percentage down — committed, dated, unfixable. Then ask the machine to attack it. If it agrees, note the hit. If it disagrees, one of you is wrong, and finding out which is a second workout — often better than the first, because now something is at stake. Puzzles are the safest ring there is for practicing this: unlike essays or strategies, a puzzle has ground truth, frequently checkable by enumeration. Part IV's forecast was that verifying confident machine output is becoming, durably, human work. Here you can rehearse that work with the answer key in the back of reality.

Coach the journal. Once a month, hand the machine your mistake journal and ask one question: "What pattern am I not seeing?" Summarizing a hundred small failures into three habits is precisely the kind of task it does well — and the diagnosis costs it no struggle you needed for yourself.

The prohibition: never read its solution first. Not as etiquette — as mechanism ⚙. The struggle is the training stimulus; the solution is the anti-stimulus. Outsource the struggle and you keep the weakness, permanently, with excellent production values.

Sparring partnerCrutch
Variants before solvingSolutions before struggling
Attacks your committed answerAnswers instead of your attempt
One-sentence hint, on request, after 30 minutesWalkthrough by default
Finds patterns in your journalReplaces the journal

One symmetry deserves saying out loud: the machine is confidently wrong in exactly the way your calibration log is teaching you not to be. Keep a hit rate on its verdicts the way you keep one on your own intervals. Two calibration curves, one desk.

Train exactly what is durable

Chapter 13 mapped the moats. Every instrument in this chapter was chosen to sit on one:

The moat (Ch 13)The training (this chapter)
Knowing you don't knowThe calibration log; a confidence tag on every answer
Continual learningThe journal plus spaced misses — you update daily; models, as of July 2026, mostly update between versions ⚖
Learning efficiencyUpsolving — maximum extraction from a sample size of one failure
Taste, and choosing what mattersThe ladder you pick, the setter's mind of Ch 8, what you keep in maintenance
Ownership and accountabilityYour name on the journal; your percentage on every answer

Nothing here needs an institution, a subscription, or a wearable. It needs twenty to forty minutes a day, a notebook, and a tolerance for being visibly wrong on paper — the one price fluency never asks and learning always does.

Chapter 16 is this chapter with dates on it.

บทถัดไป · 21 / 21The Thirty-Day Regimen
Size
Page
Font

Natural Intelligence — A Field Manual of Human Wit

❦
100 Titlepages2How to Use This Book3Introduction — The Case for Wit4Appendix C — The Reserve Rack {#appC}5Appendix A — The Moves Index {#appA}6Riddles at the Gate7The Golden Age8Thinking About Thinking9Breaking the Frame10Pure Deduction11Numbers, Chance, and Shape12The Boss Room13How Champions Think14The Kill Shots15The Builder's Tools16The Modeler's Eye17The Scoreboard18The Moats19The Race20Training the Edge21The Thirty-Day Regimen