Saying No — Capacity, Refusal & Sustainable Pace

The inverse skill stack. Say no to incoming requests so the work you committed to can actually finish — with a commitment ledger that surfaces your real no-rate, a pre-written no-script library for the request types you actually face, and categorical refusal policies that are cheaper than per-request decisions. Underneath it: energy management (hours are not fungible) and the multi-decade pace that doesn't require burnout-recovery quarters. Saying no is admission control: capacity is finite; admitting requests beyond it guarantees degraded service for everything already admitted. The commitment ledger is the audit log — without it you notice the dramatic regretted yeses and miss the structurally larger problem, the steady drift of small yeses, exactly the way a quiet elevated error rate hides without logging. The senior engineer already has the core move: scope rejection in code review. "This is good, but it's not what we agreed to ship in this PR — let's split it out and prioritize it explicitly." That sentence, which you say comfortably about code, is McKeown's graceful no verbatim. The module is largely the discovery that you already know how to do this in one domain and have been refusing to port it. And commitments are state. Good engineering keeps state minimal, explicit, and reviewable; most engineers' commitment state is the opposite — implicit, held in memory, accumulated without review, leaking. The ledger converts implicit personal state into explicit, auditable state. Energy management is workload-aware scheduling (CPU-bound tasks when CPU is fastest); sustainable pace is thermal management — run hot too long and the system throttles or shuts down for forced cooling, undoing the gains. The marathon pace is not modesty. It's the only configuration that doesn't thermally throttle over 40 years.