Breaking a large subject into small tasks, and building it as software

SLOP3733 · Week 9

You have built both halves now

And the temptation is to think of them as two versions of the same thing.

They are not, and using one where you needed the other is the most common way all of this falls apart.

What each one covers, and the hole between them

The ladder buys you the inside of thirty minutes

Absolute focus and fast feedback while you are sitting there. Nothing else does that as well.

What does it offer over a semester? Honestly: encouragement. A plain, unadorned confidence from a number you trust going up.

That is not nothing. It is also not a plan.

The ladder cannot break a large task into small ones

It never could. Rating systems rank performances

And no amount of tuning will give one an opinion

A rating system has no view about what you should do next. That is not a gap in the implementation you wrote; it is what the structure is.

So getting started, and getting small, live in the Souls half.

And neither one of those is planning

Nobody sits down in front of a new boss and decomposes it. You walk through the fog and you die in ninety seconds.

Ninety seconds gets you one observation, because that is all it has room to carry. So the next attempt has one new goal. Then the next has one more.

Twenty attempts later the boss is dead and you never made a plan.

Decomposition was an output of the attempt cycle, not an input to it.

Which is why it works on a subject too hard to start, where any plan written on day one is a guess off the table of contents.

So build the tree as a record, not as a plan

Three properties, and they all follow from that

It rolls up. A boss’s remaining work includes its children’s. Mark a parent done while its children are open and the tree is lying to you — and it will lie in the flattering direction.

It survives subdivision. Halfway through, a boss turns out to be three bosses. That is the fight becoming legible, not a failure.

Nothing has a length you fixed in advance. Estimate the work and let the duration fall out of it.

That last one is the one I would fight for

A campaign’s length is a forecast that moves when the load moves. Never a commitment you made at the start.

Fix the length up front and you have not set yourself a campaign. You have sentenced yourself to a term, and the difference is the whole reason one of them is bearable.

The unit that finally holds a result

A sitting is thirty minutes. A boss might be a hundred hours.

A day is the unit we all reach for, and a day is too short to contain a result worth feeling anything about — which is why so many evenings end with nothing to point at.

The unit that works is several days. Long enough that something finishes inside it, short enough that you can see the far end from where you stand.

So: pick a handful of bosses, and do not put a date on it

Declare them the current push. When they are done, close it and start another.

A few days is enough time to become noticeably different at something, and that is the feeling you have been missing.

Assessment 2 demonstrations

Second half. About six minutes each.

Paper or coded, and you may have chosen differently from Assessment 1 — several of you should have.