~/07
Standards
What "Production Ready" Should Mean to a Founder
Everyone agrees the product should be production ready. Almost nobody has written down what that means — which is why it is never quite finished.

~/ Blog 7 articles
Engineering decisions, written for the person who signs off on them rather than the person who implements them. No code, no jargon — money, timelines and risk.
~/07
Standards
Everyone agrees the product should be production ready. Almost nobody has written down what that means — which is why it is never quite finished.

~/06
Checklist
No code, no jargon, one conversation. Seven questions that tell you more about your engineering risk than any status report will.

~/05
Options
Four options, four different problems solved. Most founders pick by price and discover six weeks later they bought the wrong thing.

~/04
Hiring
You cannot assess the thing you are hiring for. That is a solvable problem — but not by asking better interview questions.

~/03
Investors
Funds leading $500k+ rounds increasingly read the code before they wire. Here is what they open first, and which findings cost you money rather than the deal.

~/02
Decisions
Every engineer who inherits someone else code wants to rewrite it. Sometimes they are right. Here is how to tell, using numbers you already have.

~/01
Funding
Nothing broke. The conditions changed. A product built by one person at speed works until a second person has to read it — and that is usually the week after the round closes.
