I think the author of this article should read the Mythical Man Month (https://en.wikipedia.org/wiki/The_Mythical_Man-Month https://en.wikipedia.org/wiki/The_My

I think the author of this article should read the Mythical Man Month (https://en.wikipedia.org/wiki/The_Mythical_Man-Month https://en.wikipedia.org/wiki/The_Mythical_Man-Month), in particular on the difference between (all quotes are from that book) - a program, “complete in itself, ready to be run by the author on the system on which it was developed” - a programming product: “a program that can be run, tested, repaired, and extended by anybody. It is usable in many operating environments, for many sets of data” - a programming system: “a collection of interacting programs, coordinated in function and disciplined in format, so that the assemblage constitutes an entire facility for large tasks“ - a programming systems product: “This differs from the simple program in all of the above ways. […] But it is the truly useful object, the intended product of most system programming effort” They all have their place, and if you need a program, spending time on writing a product, a programming system or a programming systems product is a waste of effort. Most scientific code falls in the program or, maybe, somewhat in the direction of the programming product category, and there’s nothing wrong with that. (Note that quality is a concept that’s orthogonal to this distinction)