Notes on making things that last
06.12.25On durable tools, quiet defaults, and the value of leaving systems understandable.
There is a particular kind of software that improves with use. It rarely announces itself. Instead, it becomes familiar: its defaults feel sensible, its failure states are legible, and its complexity stays available rather than imposed.
Durability is mostly restraint
A lasting system does not need to anticipate every future. It needs clear boundaries and enough structure that the next person can understand why things are where they are.
- Prefer fewer concepts.
- Make state visible.
- Document decisions, especially the unpopular ones.
- Leave useful escape hatches.
The most durable abstraction is often the one that makes the underlying system easier to see.
Build for maintenance
The people maintaining a system are part of the system. Comments, logs, tests, and migrations are interfaces for that future work.
Good software leaves room for care.