31 December 1999, 11:59 pm. The world holds its breath. For years, chaos has been announced: banks frozen, planes grounded, power plants down.
The problem was simple and absurd. In the 1960s and 70s, to save memory that cost a fortune, years were stored on two digits. “99” for 1999. At midnight, “00” might be read as 1900.
So thousands of developers spent years correcting millions of lines of code. Retired COBOL programmers were called back. Hundreds of billions of dollars were spent worldwide.
Midnight struck. Nothing happened. A few isolated bugs, no chaos.
And the very next day, the verdict fell: “It was exaggerated. All that for nothing.”
No. All that so that nothing would happen.
The prevention paradox
It is probably one of the greatest successes in the history of computing, and it is remembered as a false alarm. This has a name: the prevention paradox. When prevention works, there is nothing to see, so it looks as if it was not needed.
Software has not changed since. A form that does not crash, nobody notices. A page that loads instantly, nobody mentions. A data migration without incident, nobody says thank you. Only what breaks is visible.
The consequence is uncomfortable: the better the work, the less visible it is, and the more its price looks suspicious.
Making the invisible visible
The answer is not to leave a few bugs in to look busy, tempting as it may be. It is to show what cannot be seen:
- The problems avoided, not only the features delivered.
- The decisions, not only the result: why this was built this way, and what the alternative would have cost.
- What would have happened otherwise, explained before it happens rather than after.
This is why our demos and financial updates do not stop at “here is the new screen”. They also say what was secured, updated or prevented along the way.
What it means for you
When you pay for maintenance and nothing happens, it is working. You should not have to take that on trust, though. A client does not pay for what they see. They pay for what they understand, and making it understood is part of the job.