[{"data":1,"prerenderedAt":80},["ShallowReactive",2],{"blog-on-simplicity":3},{"id":4,"title":5,"article":6,"body":7,"date":67,"description":68,"extension":69,"meta":70,"navigation":71,"path":72,"readingTime":73,"seo":74,"stem":75,"tags":76,"__hash__":79},"content\u002Fblog\u002Fon-simplicity.md","On simplicity",1,{"type":8,"value":9,"toc":60},"minimark",[10,14,22,27,34,37,41,44,47,50,54,57],[11,12,13],"p",{},"There is a common misconception that simplicity means doing less, or removing features, or leaving things out. This couldn't be further from the truth.",[11,15,16,17,21],{},"True simplicity — the kind that feels inevitable when you encounter it — is the result of deeply understanding a problem. It requires you to go through complexity, not around it. You have to hold the full weight of what something could be, and then make careful, sometimes painful decisions about what it ",[18,19,20],"em",{},"should"," be.",[23,24,26],"h2",{"id":25},"the-cost-of-simplicity","The cost of simplicity",[11,28,29,30,33],{},"Dieter Rams understood this. His ten principles of good design are not a checklist for making things minimal. They are a framework for making things ",[18,31,32],{},"honest",". \"Good design is as little design as possible\" does not mean the designer did little work. It means the designer did so much work that the result appears effortless.",[11,35,36],{},"This is the paradox at the center of every meaningful design decision: the simpler the outcome, the harder the process. The reason is mechanical, not mystical. You cannot decide what to throw away from a room you have not entered. Reduction is impossible without first carrying everything — every option, every edge case, every user you imagined. The minimal answer is the one that survives after you have held all the others in your hands and put them down on purpose.",[23,38,40],{"id":39},"reduction-as-a-practice","Reduction as a practice",[11,42,43],{},"I've found that the most useful question in any design process is not \"what should we add?\" but \"what can we remove?\" Not as a cost-cutting exercise, but as a form of respect for the person who will use what you make.",[11,45,46],{},"Every element on a screen is a demand on someone's attention. Every feature is a promise you have to keep. Every option is a decision someone has to make. When you remove something, you're not just making the interface cleaner — you're giving someone back a small piece of their cognitive freedom.",[11,48,49],{},"Call this the cost of options. The user always pays it — in attention, in hesitation, in trust spent on choices that should never have been theirs to make.",[23,51,53],{"id":52},"the-discipline-of-restraint","The discipline of restraint",[11,55,56],{},"Restraint is not a natural instinct. We want to show our work. We want to demonstrate capability. But the moment a design starts to feel like it's trying to impress you, it has already failed.",[11,58,59],{},"The goal is not invisibility. It is inevitability. A simple thing is one the user could not imagine being any other way — not because it disappeared, but because it answered the question they came with so completely that no other shape was left to consider. Here is a test: if you cannot draw your own interface from memory, neither can the people who use it. The fix is not to label things better. It is to make fewer things.",{"title":61,"searchDepth":62,"depth":62,"links":63},"",2,[64,65,66],{"id":25,"depth":62,"text":26},{"id":39,"depth":62,"text":40},{"id":52,"depth":62,"text":53},"2026-03-20","Simplicity is not the absence of complexity — it is the resolution of it.","md",{},true,"\u002Fblog\u002Fon-simplicity","4 min read",{"title":5,"description":68},"blog\u002Fon-simplicity",[77,78],"design","philosophy","16Pdkm4hzUQyFTqx8wvRWiAAKv9pm_pwxz-L9-YMp7o",1776423304193]