Ming the Mechanic:
Software that lasts 200 years

The NewsLog of Flemming Funch
 Software that lasts 200 years2004-07-23 16:12
by Flemming Funch

Dan Bricklin writes about software that might last for a really long time.
In many human endeavors, we create infrastructure to support our lives which we then rely upon for a long period of time. We have always built shelter. Throughout most of recorded history, building or buying a home was a major starting step to growing up. This building would be maintained and used after that, often for the remainder of the builder's life span and in many instances beyond. Components would be replaced as they wore out, and the design often took the wear and tear of normal living into account. As needs changed, the house might be modified. In general, though, you thought of a house as having changes measured in decades.

Likewise, human societies also create infrastructure that are built once, then used and trusted for a long period of time. Such infrastructure includes roads, bridges, water and power distribution systems, sewers, seaports and airports, and public recreational areas. These also would be used and maintained without major modifications after they were built, often for many decades or even centuries.

By contrast, software has historically been built assuming that it will be replaced in the near future (remember the Y2K problem). Most developers observe the constant upgrading and replacement of software written before them and follow in those footsteps with their creations.
So, how about if we started building software as infrastructure that was meant to function for a great many years, despite changing conditions? Not that he provides the answers for exactly how to do that, but it is a call to think bigger.

It is not just about the software itself, of course. It is also about the format and media of data for example. A piece of paper can last hundreds of years. A digital CD surprisingly starts rotting within 10 years or so. It seems like we have access to 'everything' on the net and in various databases. But really we only have access to the most recent stuff, that happens to have been made in a recent format that still is popular. Only fairly rarely do we go back and convert the old stuff into the new formats.

Anyway, he specifically calls for the development of an different 'ecosystem' for societal infrastructure software. Certainly makes sense, as our societal infrastructure increasingly is totally dependent on databases and software. Makes the whole foundation of our society kind of shakey if it is based on pieces that stop working after only a few years.

[< Back] [Ming the Mechanic]



24 Jul 2004 @ 10:46 by Bob Hiltner @ : Changing capabilities, changing needs...
Taking the time to think things through in terms of design, creating good component, keeping the general engines and controllers separate... these things can extend software longevity and keep things from getting bound up so early.
But the counter factor I see is that it's difficult to span generations with useful technology infrastructure. NASA is using software many generations old, but is also basing things on 4-bit or 8-bit processors--still functional, but might as well be cuneiform. I thing that with 7-year (pick a number) generations of hardware, bandwidth, other capability, that even very well designed systems would be lucky to survive more than 10 years of the downpour of new technologies and demands. Even bridges need repainting every year and resurfacing every 10.

Protocols have spanned generations or hardware and software, but only those that have been very general and simple. The glue and caulk and user interfaces probably will always be like the paint on the bridge.

Maybe it's the glue, caulk and user interaction that is the one that nee  

24 Jul 2004 @ 12:04 by ming : Abstraction
I suppose what could survive changes in technology is something at a higher level of abstraction. Some form of representing business processes, or public database characteristics. Yeah, anything that's stuck with a number of bits or any dependence on partulcar processors and peripherals will not survive.  

20 Dec 2014 @ 01:46 by Vale @ : AqfQLVUknUspLEyzRUr
Tell me about it!1981'இல ந ங கள நங கநல ல ர க க க ட வந த ப த ஏகத த க க ம க ல மன கள ! க ணற கள ல 20-25 அட கள ல தண ண ர (உப ப த தண ண த ன !). க ர க க ட வ ள ய ட வதற க ஏற ற இடம க இர ந தத !ப னவ ரம அத நங கநல ல ர ப ர த தப த , shock and awe! Shock 99% and 1% of awe!1996'இல நங கநல ல ர வ ட ட அம ர க க வ ற க வந த ப றக அட ய ளம த ர ய த அளவ ற க நச ங க வ ட டத !அத சர ! ஹ ந த க லன என பத ச வ ல ஏவ ய ஷன க லன க க ப ன ப றம வர ம ? ந ங கள ஒர 9 வர டம Civil Aviation Colony'இல க ட இர ந த ம !! ப றக இரண ட இடங கள க க ம ற கட ச ய க லக ஷ ம நகர க க ச ட ட ல ஆக ய ர க க ற ம !!In all, not a proportionate gwotrh, I should say! BTW, ந ங கள க ற ப ப ட ம மழ த தண ண ர ந ங கள க ட ய ர ந த 19-வத த ர வ ல ம ஓட ம !! அப ப த என வயத ஒத த ச ற வர கள ம ன ப ட த த வ ள ய ட வ ர கள !பல வ ஷயங கள ச ல லல ம ! எல ல வற ற ய ம ந ங கள ச ர க கம க க ற ப ப ட ட வ ட டத ல no more comments!  

23 Dec 2014 @ 19:27 by Andreina @ : nuoILsUWMm
What a neat arteilc. I had no inkling.  

Other stories in
2012-01-24 00:50: Intellectual Property
2011-11-03 16:51: Seeing the world through the Internet
2009-06-11 18:53: Blogging/Microblogging and work
2008-02-23 17:19: Web 1, 2, 3 and 4
2008-02-22 11:07: Illusion
2008-01-09 22:45: A Communication Model
2007-12-02 20:41: Give One Get One
2007-10-25 21:47: Static or dynamic web metaphors
2007-09-18 22:54: Rethinking blogs
2007-07-04 23:59: Scrutiny of Information

[< Back] [Ming the Mechanic] [PermaLink]? 

Link to this article as: http://ming.tv/flemming2.php/__show_article/_a000010-001325.htm
Main Page: ming.tv