Over the past twenty years, I’ve worked on all kinds of systems—from large complex installations to small independent tools. When you’ve seen enough software succeed and fail, you start to notice a clear pattern: the systems that last the longest are almost always the simplest ones.
Complexity is easy. Simplicity takes care.
It’s easy to make things complicated. When something feels slow or confusing, our first instinct is often to add another layer: another plugin, another tool, another service.
But every extra piece you add is another piece that can break down later.
I prefer a calmer approach:
1. Keep it as small as possible
If you can do something with a few lines of clean, simple code, you don’t need a heavy package with a hundred dependencies. Smaller code is easier to read, easier to fix, and runs much faster.
2. Make things easy to understand
If someone else (or future you) can’t look at the project and understand what it does in a couple of minutes, it’s too complicated. Clear names and simple logic beat clever tricks every single time.
3. Treat people with care
Good software should feel gentle to use. It shouldn’t crash, it shouldn’t demand your constant attention, and it shouldn’t make you feel overwhelmed.
Building things that last isn’t about showing off. It’s about being patient, caring about the details, and choosing calm over complexity.
