4 ms·
I would tend to agree and would classify those reasons you stated as the "right technical risk" category. Although I don't think it's quite as bad as anything n
by bumby 6y ago
I would tend to agree and would classify those reasons you stated as the "right technical risk" category.
Although I don't think it's quite as bad as anything not being explicitly allowed is deemed illegal. It's not quite that strict, project managers can modernize just within certain limits (e.g., you can't just host on any cloud, but must be on a government approved cloud service).
However, I have worked in some of those environments where programmers refused to change, admittedly due to their unwillingness to learn despite their customer wanting the change. Even at organizations with large risk-adverse datasets, there's a desire to change but an inability to execute. The VA for example, has struggled for decades to modernize their system despite sinking millions and millions of dollars into it.
>If it's running now, it'll most likely continue to run for the next 20 years of software and hardware updates.
This is fine if the system is expected to remain static. Problems often arise when hardware or software are expected to change and still run the same legacy code.
- rbanffy 6y ago> Problems often arise when hardware or software are expected to change and still run the same legacy code. One of the selling points of IBM mainframes is the pretty flawless backwards compatibility. I wouldn't be surprised if you could run unmodified binaries compiled for the 360 model 20 on a z15.