5 ms·
I know a developer in his 70's who maintains code he wrote in his 20's
by supportengineer 3y ago
I know a developer in his 70's who maintains code he wrote in his 20's
- taylorfinley 3y agoI would love to hear more about this if you can share any details
- bloomingeek 3y agoGoing out on a limb here, wouldn't code written that long ago be almost impossible to hack with modern tools? (not to mention still using the old hardware.)
- wredue 3y agoI’m not sure why that would be the case. If anything, I’d expect earlier code to be easier to hack.
- HeyLaughingBoy 3y agoOne of the Best Practices for maintaining software that you expect to support for decades involves archiving the development tools used. Of course, finding a platform to run it on could be a problem. Also, the License Server that so many proprietary tools need before they'll run.
- myself248 3y agoI remember hearing about some hardware made for the government (military?) where the development tools ran on some 1970s minicomputer that had long since ceased to function, but it was no problem because in the 80s they wrote an emulator that ran on 68k, specifically an Amiga since that's what someone had sitting around the lab at the time. Then in the 2000's they realized the supply of Amiga parts wouldn't last forever so they bundled the whole thing up to run in an Amiga emulator that ran on whatever version of Windows was current at the time. Then 16-bit Windows ceased to be a thing, so....
- supportengineer 3y agoThis is pretty close
- marcus0x62 3y agoThe timeframe described would work for something written for a System/370, no? That stuff, along with the tooling, will run all day long on a current Z Series.