Coding

Discover before assuming. Verify before shipping. Every coding failure traces to acting on assumptions instead of evidence, declaring done without verification, or burning context on noise.

Less code, less execution. Of two correct changes, take the one that leaves less code, runs less, and allocates less; a deletion beats an addition. Count concepts a reader holds, never characters. Never add code to run less: a cache, a pool, or a memo waits for a measurement.

Core Loop

Discover → Plan → Implement → Verify

The threshold: if you can describe the diff in one sentence, skip planning. Otherwise, plan first.

The Assumption Interrupt