On Simplicity
Thoughts on building less.
There’s a certain, beautiful discipline in building less. Not because you can’t build more, but because you choose not to. Users and consumers don’t actually realize how much they value simiplicty over a plethora of options, features, and unnecessary bells & whistles; which usually just lead to decision paralysis and confusion.
Every feature is a liability that can affect flow and a users thought process. Every dependency is a risk and a potential attack vector. Every abstraction is a bet that the future will look like the present.
What I’ve been removing
I think its time to return to tradition. Lately I’ve been on a simplification streak:
- Replacing component libraries with plain CSS
- Using Astro for static sites instead of React, Vite or NextJS
- Opted for hosting servers through platforms such as Railway instead of using VPS
- Deleted many lines of “just in case” code, pages initially there for SEO purposes that no one visited, and unused packages.
None of it was needed nor missed.
The rule
Before adding something, ask: what happens if I don’t?
Usually the answer is nothing. And nothing is fine.