A slow software manifesto

A small tool doesn't need growth hacking. Make it for yourself, open-source it on the way, and that's enough.

I like slow software: it doesn't chase you for notification permissions, doesn't nag you to upgrade, and doesn't need a funding story. It solves one small, specific problem and then quietly stays out of the way.

If one day it helps someone else, that is a bonus, not the goal.

So I gave myself a few rules: one tool does one thing; work offline whenever possible; keep the data in the user's hands; keep the code short enough to still understand a year later. Slow is not inefficient — it just leaves room to think about each decision.