Every few months a new tool arrives promising to change everything, and every few months I watch small teams adopt it, drown in it, and quietly go back to spreadsheets. The tool was rarely the problem. The problem was that nobody asked what the team was actually trying to do.
I hold every build to a simple test: after I leave, does the team feel more capable or more dependent? Software that requires me forever is a lease, not an asset. The organizations I serve deserve assets.
That test changes how you build. It means choosing boring, durable platforms over impressive fragile ones. It means writing documentation nobody asked for. It means training the owner until they can break and fix the thing themselves. It means designing the handoff from day one.
Empowerment is not a soft goal. It is a hard engineering constraint, and honoring it is the difference between technology that serves people and technology that quietly becomes their second job.
Essays like this land in the journal first and on Substack soon after.
Subscribe on Substack