Jake Voytko pushes back on nostalgia for a golden age of software quality. His memories of everyday computing include unstable drivers, lost documents, malware, and installations that depended on an undamaged disc. Modern software has plenty of faults, but several old failures have become much harder to inflict on users.
- Recovery used to be the user’s job. Crashes and unreliable autosave made constant manual saving a survival habit.
- That habit outlasted the problem. On the Google Docs team in 2010, Voytko saw Ctrl+S rank among the most common non-editing actions. The shortcut only recorded a metric; Docs already autosaved.
- Maintenance became part of using the computer. People manually defragmented disks and cleaned up systems that had become painfully slow.
- Hidden assumptions reached the interface. Programs tied to processor speed needed a hardware slowdown button. Online games that trusted clients invited cheating and abuse.
- Better defaults removed whole chores. Process isolation, online updates, higher-level languages, and clock-based timing address recurring sources of failure.
Software quality includes how much vigilance a system demands from its users. Preserving work, containing failures, and handling routine upkeep can matter more than a tidy implementation that leaves those responsibilities outside the program.
Voytko offers a personal history, not a measured comparison across eras. It still gives teams a concrete review question: which recovery ritual could the next version make unnecessary?