Of course, there are also software engineering errors that cause incorrect outputs from the model to be provided, and incorrectly high confidence to be attached to those predictions. But, given the kinds of errors commonly seen in similar fields (e.g. physics engines), I would expect the probability of those kinds of error to be far outweighed by the other kind, the 'clear errors' where the model encounters out-of-tolerance data, and can then either bail out or "taint" all computations going forward.
The vast majority of all models that ever get written are done in academia like nuclear simulation models or geological models or whatever. In college I worked in high performance computing which led me to write software in academia for blast simulations and for genetic sequence alignment. Both share lots of the traits that the author outlined, but neither had to do with climate.
Just because your situation isn't a business doesn't mean you're unique.
"Because there are many other modeling groups, and scientific results are filtered through processes of replication, and systematic assessment of the overall scientific evidence, the impact of software errors on, say, climate policy is effectively nil."
The commenter seemed to completely ignore the explanation, and took the quote out of context. The rebuttal was answered in the original statement.
1. There's probably a considerable amount of overlap between the software used by different research groups. The article says:
"Single Site Development – virtually all coupled climate models are managed and coordinated at a single site, once they become sufficiently complex, usually a government lab as universities don’t have the resources"
Which implies that several university research groups use the software being maintained by a handful of large labs. They might be running models with different parameters, but the underlying modeling software is the same. So an error in the software might be widely propagated across hundreds or thousands of research papers. Also new scientific results frequently build upon previously published research, so anyone who cited a buggy result as evidence may have a weaker case.
2. If other scientists have similar attitudes toward writing software (i.e., that climate software is "different" from other software), they're also not likely to be using the best practices of software development, and much of the modeling software in the world is likely to be unreliable. In that situation, how would you be able to figure out which modeling software is giving the correct result?
As that commenter wrote in another comment:
"Unfortunately, I have encountered the following argument a distressing number of times:
1. As a good scientist, I am automatically a good engineer.
2. As a good engineer, I am automatically a good programmer.
3. As a good programmer, I am automatically a good Software Quality Assurance Analyst (whatever that is, nothing significant I would guess).
What hubris. Programming is a domain in its own right. It’s the most complicated domain there is because if people could make their programs any more complicated they would. Programming is also an art. Even a computer science degree does not make you a good programmer."
The author seems to have a rather cavalier attitude about the correctness of code, which one of the commenters (George Crews) picked up on:
"Then there is the statement: 'The software has huge societal importance, but the impact of software errors is very limited.' I don’t see how it can be both ways. How can something be of great importance whether or not it is correct? IMHO, the most serious consequence of a climate software being defective would be to then use it to make a defective political decision costing trillions of dollars to society."