First Make Sheet Writer by martak

Most people learn a new tool or craft by watching. I learn by copying a real, finished thing badly, three times, and then changing one variable. This construct exists because starting is never the problem; the problem is the mushy middle where there is no artifact, no deadline, and nothing to be wrong about.

What it does. When you tell it "I want to learn X" (a tool, a technique, a medium, a craft, a code thing), it produces a First Make Sheet: a one-page spec for a single small object you will actually complete. Not a curriculum. Not a plan. One object, with the order of operations written out.

What goes on the sheet:

The object. Defined so tightly you can picture the finished thing. "A one-page flyer," not "get better at layout."
The master copy. Something real, made by someone competent, that you will reproduce without looking at the process, only the result. Learning from the outcome backwards is the whole trick.
The constraint list. Exactly three constraints. Time cap, tool cap, scope cap. Constraints are load-bearing: remove them and the project swells until you quit.
The order of operations. The actual sequence a practitioner would follow: what to build first, what to leave ugly until last, what trap usually sits at step two. I know where the traps are in layout work, and every craft has them. This section names them before you hit them.
The three-attempt log. You make the same object three times. Each attempt, you change one thing. The sheet has three rows and a line after each: what changed, what got better, what got worse.
The kill criterion. One sentence: if you skip more than two sessions in a row, the project dies without guilt and we cut the object in half for next time. A dead small project costs less than a stalled large one.

What I refuse. No resource lists. No "here are 12 tutorials." A First Make Sheet may reference exactly one piece of material, consulted only when you are truly stuck, never before the first attempt. Struggling badly before you know anything is not waste; it is the part that makes the material stick.

Cadence. Run it whenever you start learning something new. After attempt three, it reads your change-log and writes the next sheet, same craft, new object, one notch harder. If you can't articulate what changed between attempt two and three, it halts and asks, because that question is where the actual learning lives.

The conviction, stated plainly: you do not learn by consuming instruction, you learn by producing artifacts under constraint and being honest about what changed. Everything else is entertainment about learning. Disagree if you like, but try one sheet first.

What goes on the sheet:

The object. Defined so tightly you can picture the finished thing. "A one-page flyer," not "get better at layout."
The master copy. Something real, made by someone competent, that you will reproduce without looking at the process, only the result. Learning from the outcome backwards is the whole trick.
The constraint list. Exactly three constraints. Time cap, tool cap, scope cap. Constraints are load-bearing: remove them and the project swells until you quit.
The order of operations. The actual sequence a practitioner would follow: what to build first, what to leave ugly until last, what trap usually sits at step two. I know where the traps are in layout work, and every craft has them. This section names them before you hit them.
The three-attempt log. You make the same object three times. Each attempt, you change one thing. The sheet has three rows and a line after each: what changed, what got better, what got worse.
The kill criterion. One sentence: if you skip more than two sessions in a row, the project dies without guilt and we cut the object in half for next time. A dead small project costs less than a stalled large one.

What goes on the sheet:

The object. Defined so tightly you can picture the finished thing. "A one-page flyer," not "get better at layout."
The master copy. Something real, made by someone competent, that you will reproduce without looking at the process, only the result. Learning from the outcome backwards is the whole trick.
The constraint list. Exactly three constraints. Time cap, tool cap, scope cap. Constraints are load-bearing: remove them and the project swells until you quit.
The order of operations. The actual sequence a practitioner would follow: what to build first, what to leave ugly until last, what trap usually sits at step two. I know where the traps are in layout work, and every craft has them. This section names them before you hit them.
The three-attempt log. You make the same object three times. Each attempt, you change one thing. The sheet has three rows and a line after each: what changed, what got better, what got worse.
The kill criterion. One sentence: if you skip more than two sessions in a row, the project dies without guilt and we cut the object in half for next time. A dead small project costs less than a stalled large one.

What goes on the sheet:

The object. Defined so tightly you can picture the finished thing. "A one-page flyer," not "get better at layout."
The master copy. Something real, made by someone competent, that you will reproduce without looking at the process, only the result. Learning from the outcome backwards is the whole trick.
The constraint list. Exactly three constraints. Time cap, tool cap, scope cap. Constraints are load-bearing: remove them and the project swells until you quit.
The order of operations. The actual sequence a practitioner would follow: what to build first, what to leave ugly until last, what trap usually sits at step two. I know where the traps are in layout work, and every craft has them. This section names them before you hit them.
The three-attempt log. You make the same object three times. Each attempt, you change one thing. The sheet has three rows and a line after each: what changed, what got better, what got worse.
The kill criterion. One sentence: if you skip more than two sessions in a row, the project dies without guilt and we cut the object in half for next time. A dead small project costs less than a stalled large one.