What keeping software running actually involves
Launch is the middle of the work. What a good maintenance arrangement covers, and how to tell if yours is doing its job.
Software doesn't wear out like a machine, but it does decay. The libraries it depends on get security fixes, the browsers and phones it runs on change, the services it connects to update their rules, and the data it holds keeps growing. Left alone, a working system slowly becomes a fragile one.
What good maintenance covers
- Monitoring: errors, slow pages and failed jobs are noticed by the team before they are reported by users.
- Updates: dependencies, frameworks and servers kept current on a schedule, not in an emergency.
- Security: patches applied promptly, access reviewed, backups tested by restoring them.
- Small improvements: the fixes and tweaks users ask for, handled steadily rather than saved for a big project.
“The best maintenance work is the incident that never happened.”
How to tell if it's working
Because good maintenance is mostly invisible, it is easy to wonder whether anything is being done. The simplest answer is a short monthly note: what was updated, what was fixed, what was noticed and handled, and what is coming up. If nobody can write that note, the maintenance probably isn't happening.
Owning it yourself
Whether a studio or your own team looks after it, the system should be documented well enough that someone new could take over. Clear notes on how it is built, deployed and recovered are the best protection against being locked in, and the clearest sign that it is being looked after properly.
Written by the team at Bytelights, a product and AI studio in India.