3 ms·
> What do we do? Keep rewriting everything every 50 years? Yes, or sooner. And you keep the 'institutional knowledge' externalized in documents, and you use t
by lowercased 7y ago
> What do we do? Keep rewriting everything every 50 years?
Yes, or sooner.
And you keep the 'institutional knowledge' externalized in documents, and you use testing tools and use virtualized systems and what not (virtual systems were available to consumers even 20 years ago - this is not that new).
"Upgrade" or "rewrite" every 10-15 years. This should just be a cost of maintenance. I'm at the point where I've had PHP code running on systems for 15+ years (had a call from someone in 2017 about software started in 2002 and last touched in 2004). There's a 'on the public internet' distinction with web apps vs internal bank systems, for example, agreed, but it doesn't remove the need for upgrading old systems. Doing it on your own schedule, on your own terms, vs having to deal with systems in crisis, is where the benefit is.
- sedachv 7y ago> and you use testing tools and use virtualized systems and what not "what not" has been running in production since 1972: https://www.ibm.com/it-infrastructure/z/zvm https://www.ibm.com/it-infrastructure/z/zvm
- lowercased 7y agosure... I know my experience of virtualization tools is relatively limited, but I was using consumer versions of VMWare in .... 1999 IIRC. These ideas aren't terribly new.