Worse Is Better: The Art of Simplistic Design
What Is Good Design?
Today’s Lens: Richard P. Gabriel — “Worse Is Better” as a Survival Strategy
“Simplicity is the most important consideration in a design.” (cs.columbia.edu)
Gabriel’s provocation: good design sometimes starts “smaller than right,” optimizing for survival and spread. In his schema, you trade a bit of completeness—and, when necessary, strict consistency—for radical simplicity and “correct enough” behavior. Why? Because simple cores travel farther: they’re easier to implement, adopt, port, and improve in the wild. Over time, the living, widely used thing can surpass the immaculate but slow-to-ship “Right Thing.” (cs.columbia.edu)
Put it to work (in minutes)
- Define a smallest promise: one sentence describing the job your v1 must do “correctly in observable aspects.” Everything else becomes optional. Ship that. (cs.columbia.edu)
- Budget completeness explicitly: list edge cases you will drop now to keep the core simple; add an “adoption-first” plan to iterate them back. (cs.columbia.edu)
- Optimize for portability and repair: prefer choices that reduce dependency count, ease fixes, and invite contributions—so the design can move and grow. (cs.columbia.edu)
- Measure survival, not polish: track time-to-first-use, successful ports/integrations, and user-led improvements as primary health metrics. (en.wikipedia.org)
Good design isn’t always the maximal answer; it’s the minimal living seed that can take root, adapt, and compound. Gabriel’s reminder: make it simple, make it work where people are, then let success pull completeness in—rather than block release until perfection arrives. (cs.columbia.edu)
—
Further reading: Richard P. Gabriel, “The Rise of ‘Worse Is Better.’” (cs.columbia.edu)