The Oncall
Ship fast, get paged at 3am: the engineer and the ops hat are the same person, six months apart.
48 published
Ship fast, get paged at 3am: the engineer and the ops hat are the same person, six months apart.
Scripture as decision tool. Bring a dilemma. Get a structured read. Each verse cites itself. Old text. New index.
The rejected list — features declined, integrations passed on — is most of the actual work.
The discipline of shipping well. Sketch before build. Review before ship. Verify before done. Atomic changes. Convention, not framework. Tool-adaptable. A /command per step. Solo, or with a thinking...
The gap between "works" and "feels right" — and the designer hat nobody certified you to wear.
Draft the message before sending. Hard things go better when said twice — once to yourself, once for real. Know what to say before you say it.
The second project is the first one's rent — proof you can maintain, not just build.
Spec first. Stack later. Describe the idea. Answer the architecture questions. Walk away with a deploy-ready zero-stack spec. $0/month is the architecture, not the budget.
Breaking your own work before anyone else does: the half of shipping nobody teaches.
AI policy, generated. Pick a preset. Tune the rules. Download AIPOLICY.md, AGENTS.md, CLAUDE.md. Drop them in the repo. The bots will read them.