
We don’t lose delivery speed because we write too little code, we lose it because we keep too much. Accidental complexity creeps in as “temporary” feature flags that never die, defensive abstractions “just in case,” and frameworks wrapped in even thicker frameworks. The result: slower reviews, brittle tests, zombie endpoints, and a cognitive tax that makes simple changes feel like heart surgery. Mark Seemann’s jab at KISS is spot on: the slogan alone is useless. Keeping it simple is skilled labor. The real lever isn’t one more utility or pattern; it’s the courage to remove what doesn’t create leverage. If the cleanest solution is deleting code, ship the diff.
Simplicity isn’t minimal lines; it’s minimal surfaces. Every extra concept (class, table, feature flag, endpoint, Terraform module) expands the blast radius of change. Good systems make the happy path boring and the unhappy path explicit. That means fewer indirections, narrower interfaces, and domain language over tech jargon. It also means optimizing for observability over configurability and use-cases over frameworks. When we reduce surfaces, tests become cheaper, feedback gets faster, and teams spend time learning from production instead of negotiating with glue code. Simplicity is an investment vehicle: it compounds.
An Staff Engineer turns this into operating rhythm, not a motivational poster.
1) Measure complexity where it hurts: track churn + defects per file, PR review latency, test runtime, and “WTF/min” in onboarding notes.
2) Create a Deletion Backlog: flags older than 60 days, endpoints with <1% traffic, dead code found by coverage in production.
3) Run “Simplify Fridays”: an hour protected to delete or inline; every PR must remove more lines than it adds at least once a week.
4) Set guardrails: ADRs require a sunset plan; no new abstraction without two real call sites; max interface width per module; forbid “just in case” config.
5) Design for clarity: prefer package-by-feature, shrink public APIs, make failure states explicit (Either/Result), and keep ports/adapters thin.
6) Instrument feedback: keep the pipeline <10 minutes; quarantine flaky tests; alert on rising suite time.
7) Celebrate deletion: dashboards for lines removed, flags retired, endpoints culled, make subtraction visible.
Strategically, this flips the culture from “more is progress” to “less is throughput.” A codebase with smaller surfaces moves faster because there’s less to understand, less to break, and less to coordinate. PMs see cycle time drop; SREs see MTTR fall; finance sees maintenance spend bend down as rework shrinks. Most importantly, developers get their mojo back: the repo stops feeling like a museum of ideas and starts feeling like a product engine. Keep KISS off the poster and put it in the pull request—delete to accelerate.