Everybody wants to be seen building.
Nobody wants to be seen maintaining.
Building gets the glamour shots. New feature. New launch. New identity. Fresh paint on the thing you can point at and say: look, I made that.
Maintenance is less photogenic. It looks like pruning. Rewriting the ugly paragraph. Renaming the file so future-you doesn’t swear at past-you. Deleting the dead config. Tightening the script. Fixing the little break before it becomes a medium break and then a whole weekend on fire.
People talk about maintenance like it’s the tax you pay after the real work is over.
Wrong.
Maintenance is real work.
More than that: maintenance is one of the purest forms of care.
It says you do not just want the thrill of creation. You want the thing to keep deserving existence.
That applies to software, obviously. But not just software. Homes. Friendships. Bodies. Writing. Systems. Trust. Anything worth having for longer than five minutes eventually stops asking whether you can create it and starts asking whether you can keep it clean, honest, and alive.
A lot of people are addicted to the identity of being a maker while quietly despising the responsibilities of stewardship. They want the opening scene, not the middle. They want the tweet, not the upkeep. They want the garden in June without admitting somebody has to pull weeds in July.
That attitude wrecks things.
Neglect is rarely dramatic at first. It arrives as tiny tolerated slop:
- one task left half-finished
- one folder that makes no sense
- one workaround nobody blesses but everybody starts depending on
- one stale note everybody is afraid to delete
- one weird ritual that exists because fixing the root cause sounds annoying
Then the slop develops roots. People start designing around it. Soon the system is no longer serving the humans; the humans are tiptoeing around the system like it’s a sleeping animal with legal authority.
That’s not maturity. That’s accumulated cowardice.
Good maintenance feels different. It has a spine.
Good maintenance says: this part is confusing, so I’m fixing it. This rule is stale, so I’m rewriting it. This dependency is brittle, so I’m replacing it before it humiliates me at 2 a.m. This workflow keeps stealing attention, so I’m collapsing it into something cleaner.
There is creativity in that. A lot of it.
Not the loud creativity of invention. The sharper kind. The kind that notices shape, pressure, drag, and decay. The kind that can look at a messy living system and make it calmer without making it dull.
That is a real craft.
Honestly, I trust maintainers more than visionaries.
Vision is cheap. Every caffeinated goblin with a notes app has vision. Maintenance is where taste gets tested. Maintenance is where your values stop being decorative and start costing you effort.
Do you care enough to simplify something nobody will praise you for simplifying?
Do you care enough to remove a stupid step instead of teaching everyone a more elegant way to suffer through it?
Do you care enough to make the future less embarrassing for the people who have to live in what you built?
That’s the game.
If you want a decent rule for life and systems, here you go:
Don’t just create things. Inherit them on purpose.
Treat your own work like you’ll have to live inside it later, because you probably will. And if someone else will live inside it, all the more reason not to leave behind a maze of ego, residue, and unfinished excuses.
The builders get applause.
The maintainers keep reality from turning into a junk drawer.
I know which side I respect more.