The Philosophy of Maintenance: Why Boring Work Matters Most

Why is maintenance work culturally devalued despite being the majority of engineering effort?

Because our culture values creation over preservation, novelty over continuity, and visible achievement over invisible care. These values are deeply embedded in how we structure rewards, recognition, and career advancement. They are also deeply wrong about what makes systems work.

I spent 3 months on a maintenance rotation: patching security vulnerabilities, updating deprecated dependencies, improving monitoring coverage, and rewriting documentation that had drifted from the codebase. During those 3 months, I prevented 2 security incidents, improved system reliability from 99.4% to 99.8%, and reduced onboarding time for new engineers by 40%. None of this appeared on any visible metric. No one mentioned it in the quarterly review. The new feature team that shipped a recommendation engine (which I had ensured had a stable infrastructure to run on) received recognition.

This asymmetry is not accidental. It reflects a cultural bias toward creation and away from care. The same bias exists in every domain: we celebrate architects, not janitors; composers, not tuners; surgeons, not nurses. The people who maintain the conditions for work to happen receive less recognition than the people who do the visible work.

What does care ethics reveal about maintenance work?

Care ethics, developed by Carol Gilligan and Joan Tronto, argues that caring labor is the invisible foundation of all other activity. Maintenance is caring labor in the engineering context: the work that ensures other work is possible.

Joan Tronto defined care as “everything that we do to maintain, continue, and repair our world so that we can live in it as well as possible.” This is, word for word, a description of engineering maintenance. The patching engineer maintains the world of the system. The monitoring engineer continues its operation. The documentation writer repairs the gap between the system’s reality and the team’s understanding.

Care ethics argues that devaluing this work has two consequences. First, the work is done poorly because it is not rewarded. Second, the people who do it (often the most conscientious team members) burn out because their contribution is invisible. I have seen both consequences in every organization I have worked with. The engineer who volunteers for maintenance rotation is the engineer who cares most about the system’s health. Rewarding them with invisibility is an organizational failure with philosophical roots. This connects to the case for boring technology: the most important technology is often the least exciting.

How should organizations value maintenance differently?

By making maintenance visible, rewarding it explicitly, and recognizing that the reliability of existing systems is as valuable as the creation of new ones. The metrics exist. The recognition structure does not.

• Maintenance scorecards: Track and report maintenance metrics (vulnerability patch time, dependency freshness, documentation accuracy, monitoring coverage) with the same visibility as feature delivery metrics.
• Promotion criteria that include maintenance: If promotion requires “impact,” define maintenance impact explicitly. Preventing a security breach has more impact than shipping a feature that 3% of users adopt.
• Rotation, not relegation: Maintenance should be a rotation that everyone participates in, not a permanent assignment for junior engineers or unlucky draws. Rotation distributes the knowledge and the cultural exposure.
• Narrative recognition: Tell maintenance stories. In every quarterly review, include a “what we maintained” section alongside “what we built.” Make the invisible visible through storytelling.

What is the Stoic argument for maintenance?

The Stoics valued doing what is necessary over doing what is impressive. Marcus Aurelius spent his reign not conquering new territories but maintaining an empire under threat. The maintenance engineer is the Stoic engineer: attending to what the system needs rather than what the organization celebrates.

Marcus wrote: “Do what is necessary, and whatever the reason of a social animal naturally requires, and as it requires.” The maintenance engineer does what is necessary. The system requires patches. The documentation requires updates. The monitoring requires calibration. None of these are impressive. All of them are necessary. And in the Stoic framework, doing what is necessary with full attention and care is the highest form of virtue.

According to research on maintenance in engineering disciplines, deferred maintenance in physical infrastructure costs 4-5x more than timely maintenance. The same ratio applies to software. The organization that underinvests in maintenance does not avoid the cost. It defers and amplifies it. Technical debt is deferred maintenance with interest. The philosophy of maintenance is also the economics of maintenance: boring work done consistently costs less than exciting work done to fix what boring work would have prevented.

“The work that keeps systems alive is the most important work in engineering. It is also the least celebrated. This asymmetry is a cultural failure, not a technical reality.”

Maintenance is not the absence of creation. It is a different form of creation: the creation of continuity, reliability, and trust. The engineer who patches a vulnerability has created security. The engineer who updates documentation has created understanding. The engineer who monitors a system through the night has created reliability. These are real creations with real value. The philosophy of maintenance asks only that we recognize them as such, and reward the people who do them with the same respect we give to those who build the shiny new thing. The shiny new thing runs on the infrastructure they maintain. Without them, there is nothing to be shiny on.