I wrote this two years ago and for some reason never published it:
Software is taking over our lives – the way we communicate, learn, play, work, and shop. I’m both thrilled and worried about that. Thrilled because now that we’ve made the mind-boggling investment of putting computers onto every desk and into every pocket and connected them all via the internet, we can build and release infinite amounts of software much more cheaply and quickly than we can build pretty much anything else. And to my delight, the original hippie dream of the technologists who envisioned all of this back in the 1960s and 1970s has largely survived the attempts of businesses and governments to take control: Our various technology platforms, in particular the internet, are largely free, open, and universally accessible to anyone who wants to build a piece of software and send it out to the world. So why am I worried? For all its benefits, software is amazingly fragile. From a creator’s point of view, it requires almost constant maintenance for it to continue to work. The pieces of software I personally run right now – a web browser, email client, a blog, etc – are between a few days and a few months old. Most of the software I ran last year or the year before no longer works, and more crucially, some of the things I created using those older pieces of software stopped working along with it. I have notebooks from grade school sitting in a closet next to me. I can pick them up and they work just fine, the same as they did 30 years ago. Yet keeping my digital documents working requires constant maintenance, backing up, and transferring to new formats, or they simply become defunct.
There’s a concept of technical debt inside software companies. It means that poor software design choices upfront lead to major maintenance hassles down the road. As software takes over our lives, we should think about how to minimize technical debt not just in companies but at a societal level, to help avoid some major risks and headaches in the coming decades.
Leave a Reply