When I started the public repo for Knot Forget, I spent a session on scaffolding before writing a single line of application code. Not just hygiene — a README, some labels, a branch ruleset — but a structure that would make every subsequent session faster than the last. This is how I set that up, and why the order matters.
Compound engineering
Compound engineering is a workflow developed and open-sourced by Every Inc. The premise is that 80% of leverage is in planning and review, 20% in execution — and that each cycle should make the next one cheaper, not harder.
The loop has four phases:
Plan — brainstorm requirements, write a right-sized spec before touching code
