Journal — Technology
Why good software feels simple.
Simplicity isn't the absence of features — it's the result of decisions made somewhere else.
Simplicity is a result
Users experience simple. Engineers build complex. The distance between the two is design. Good software feels effortless because someone absorbed the effort somewhere upstream — in the data model, in the defaults, in the one workflow that matters.
Every default is a decision
The fastest way to feel the difference is to watch what happens by default. Good software does the right thing when you do nothing. That requires naming the common path and then defending it against every feature request that arrives later.
Defend the common path
Feature requests are the enemy of the common path. Each one looks reasonable in isolation; together they turn a straight road into a maze. The discipline is deciding what not to build, and saying it out loud.
Simple is not a starting point. It is an output.
Related Work
Next Article
Product