3 ms·
The problem is that the code base is byzantine with developers hired who don't have good Fortran knowledge. There are a million different versions of the same
by Marazan 11y ago
The problem is that the code base is byzantine with developers hired who don't have good Fortran knowledge.
There are a million different versions of the same function each with a minor tweak to get the "right" behaviors labeled func_name_1 down to func_name_1000000 because everyone is too scared to fix the original function as they don't know what depends on it.
It's not that Fortran is the right tool for the job it's that it has terminal momentum.
- noselasd 11y agoThough, had the same developers created the system in another language, they'd probably still be in the same mess.
- dragonwriter 11y ago> The problem is that the code base is byzantine with developers hired who don't have good Fortran knowledge. > There are a million different versions of the same function each with a minor tweak to get the "right" behaviors labeled func_name_1 down to func_name_1000000 because everyone is too scared to fix the original function as they don't know what depends on it. Sounds like a problem with development practices, documentation, and overall code lifecycle management -- and also employee management in terms of skill development priorities. Those issues aren't particularly tied to implementation language.
- ArkyBeagle 11y agoThis in specific is one of the handful of things actually tractable by testing. But don't kid yourself - we all abritrage technical debt.