Happy Code is small
Never forget why you’re really doing what you’re doing.
Are you helping people?
Are they happy?
Are you happy?
Are you profitable?
Isn’t that enough?
Software has a strange relationship with size.
When something works, we rarely let it remain what it is.
Someone sets out to solve a problem.
Then solving it stops feeling like enough.
A tool becomes a product.
A product becomes a platform.
A platform becomes an ecosystem.
Soon the original problem is almost hidden
under the ambition built around it.
Scale is not the problem.
Some systems genuinely justify it.
The problem begins when growth
stops being a consequence
and becomes the goal.
When size starts to matter more than purpose.
When reach matters more than people.
When lock-in matters more than choice.
When scaling matters more than serving.
This is the warning in Small Is Beautiful
by Ernst Friedrich Schumacher.1
Even though it was written in 1973,
it is still painfully true for software.
He was arguing for proportion.
And we are still learning that lesson.
The larger a system becomes,
the more its incentives change.
It has more markets to satisfy,
more data to exploit,
more partners to serve,
more revenue to defend.
At some point, the question can shift
from How useful is this?
to How much can this capture?
That shift is where many good tools begin to rot.
A service begins by being good to users.
Then it adjusts to better serve businesses.
Finally, it degrades the experience for both
to pull more value back to itself.2
No single change explains the whole rot.
The direction says enough.
The tool no longer asks how to help.
It asks how much worse it can become
before people leave.
That is not success.
That is decay, reported as progress.
Smallness matters
because proportional systems
leave space around themselves.
Alternatives can exist.
The people affected can still shape it.
The thing can even end
when its purpose is finished.
This is the idea of appropriate technology.
Not the most advanced technology,
but technology that fits.
And fitting is an underrated virtue.
Sometimes the fitting solution is simple.
A page.
A script.
A boring integration.
A process that needs no software at all.
It may never become a company.
It may never become a platform.
It may never become an ecosystem.
That does not make it less valuable.
Usually, that is exactly what makes it valuable.
Happy Code does not need
to win the world
to be worth writing.
It stays small.
And small stays beautiful.
E. F. Schumacher, Small Is Beautiful: A Study of Economics as if People
Mattered (1973). The book argues for human-scale economics and technology, and against treating bigness as an automatic good. ↩︎Also known as “enshittification”: the gradual decline of a platform as it extracts more value from the people and businesses that use it. ↩︎