Treating a subject as a set of bosses, on paper#
SLOP3733 · Week 8#
Last week you understood a fight you could not have described beforehand#
Twenty deaths, one line each, and at the end of it a model of a boss.
This week you do the same thing to a subject.
The instinct is to break it into parts first#
It feels responsible. It is also the move that has failed you before.
On day one you do not know enough about the subject to know what its parts are. Any list you write is a guess assembled out of the table of contents.
And a confident wrong plan is worse than no plan, because you will follow it.
Nobody walks up to a Souls boss and decomposes it#
You go through the fog, you die, and the fight tells you what it is made of
The loop, on paper. Four lines.#
- What I am attacking now. One thing, small enough to attempt today. Not understand regression — derive the normal equations from a blank page.
- The attempt. Short enough that you find out today, not next week.
- The one lesson. About the work, not about you. I can follow the derivation and cannot start it is a lesson. I was lazy is not.
- The one change for next time. Exactly one. Write three and you will not know which of them worked.
Then go again. It is deliberately too small to be impressive.
The list you would have written, and the list you got#
The list grows; you do not write it#
By attempt five it becomes clear that the reason you cannot start from a blank page is that you never learned to write down what you are minimising.
Now you have a second thing to attack — one you could not have put on a list on Monday.
A boss is something you found by attacking. If your list is complete and tidy after an hour at your desk, you have written a table of contents and given it a new name.
Some of what you find is small#
A piece of notation. A tool you cannot drive. A definition you keep mis-remembering.
Call those elite mobs, give them one line each and no ceremony, and do not let them become projects.
The games cannot agree either#
Kill conditions, written when you can#
For each thing you are fighting, write the check that ends it: one sentence, checkable by someone who is not you.
You often cannot write this on the first attempt, and you should not pretend to. Done for a fight you have never had is a guess like everything else.
What you must not do is leave it unwritten indefinitely. A fight with no kill condition stays open forever, which is the single most common way this mechanism fails.
Why any of this hurts less#
Failure becomes small, expected and local#
A hard subject hurts because failure feels total and unbounded. You do not know how much is left, so every failure is evidence about the whole mountain, and about you. That is unbearable over months.
You did not fail at statistics. You failed at starting from a blank page, once, and you already know what you are changing.
That is a survivable size.
And surviving it is the entire reason you get to attempt number twenty.
This week#
Attack something. Five attempts minimum on a real subject, logged four lines each.
Bring the log to week 9, with whatever list of fights has grown out of it — and if the list changed shape halfway through, bring both versions.