A letter, before you read

Ibuilt this because I kept losing the same lessons twice. Every project taught me something expensive, and every project buried it in a commit message nobody would ever read again — including me. So I started writing the lessons down in the only format I trust: a manual a stranger could pick up cold and still resume the work.

Six volumes came out of that. Not theory. Each one is drawn from something I actually shipped, argued with, broke, or walked away from. The claims are demoted on purpose: where something is confirmed, it says confirmed; where it is a guess, it says speculative. That honesty is the whole method. It is also the only part I would defend in a room full of people who disagree with me.

Who it's for

The solo founder holding six half-finished substrates and no one to hand them to. The engineer who inherited a system with no owner's manual and had to reverse engineer intent from behavior. The person building alone at midnight who suspects the work is good but can't prove it to anyone yet — including themselves.

It is not for people looking for growth tactics. There are none here. If your question is how to get more attention, this is the wrong shelf.

What I hope you get out of it

One clean decision. That's the bar. If a single chapter makes you delete a feature, rename a thing correctly, write the manual before the marketing, or refuse a deal that would have cost you the substrate — the library paid for itself, and it was free.

And if you take the method and never mention my name, that's fine too. Fork the method, not the identity. The volumes are sealed so you can prove they didn't drift; they are free so nothing stands between you and the part you needed.

Thank you for digging this far. Most people don't.