Re:Why bad scientific code beats code following "best practi...
by thriftwy on Saturday January 06, 2024 @02:18AM
(#38889248)
What if a new person takes your place and they do not know it and are not certain in anything?
Re:Why bad scientific code beats code following "best practi...
by o11c on Saturday January 06, 2024 @02:31AM
(#38889316)
That's how you measure job security, which is a slightly different concept than maintainability.
Re:Why bad scientific code beats code following "best practi...
by skydhash on Saturday January 06, 2024 @08:46AM
(#38891370)
When you hire a new person, there is usually some transfer of knowledge. Based on the above definition such transfer should be quick assuming that the person knows the platform and dependencies. A long time explaining the code is an indicator of needlessly complicated code
How maintainable code is is measured in how well you know where to change something, and how certain you are that it did the right thing without side effects.
The fatal error of the linked article is that bad scientific code often suffers from correctness problems - not just theoretical concerns, but the "negates the main point of this paper" kind of thing.