3 ms·
These should be separate in academia. SWEs cannot write code that maps equations that may change daily completely due to modeling / assumptions change. Too mu
by whatever1 4y ago
These should be separate in academia.
SWEs cannot write code that maps equations that may change daily completely due to modeling / assumptions change.
Too much focus on modularizing, premature optimization, useless unit testing etc. Who cares about all these if the underlying model is wrong?
If things are stable enough to go into production then the code should leave academia and be re-written properly by SWEs, not by clueless bio phds.
- sargstuff 4y agoUmm..... software weather modeling systems map equations that may change daily completely due to modeling / assumptions change.
- whatever1 4y agoFunny you mention weather because I have worked in the field. We had to make a change in the discretization scheme, and pretty much all of the assumptions of the super optimized parallelized production version had to be thrown away, to the point that we had to abandon it completely. Software engineering needs well defined boundaries to design between them and test edge cases. When we are doing fundamental research we don’t have this. Literally anything can change in the logic, the inputs, the outputs.
- sargstuff 4y ago> "Funny you mention weather because I have worked in the field. We had to make a change in the discretization scheme, and pretty much all of the assumptions of the super optimized parallelized production version had to be thrown away, to the point that we had to abandon it completely."... Ah, so initial pixilation for front fonts weren't unicode compatible? :-)