3 ms·
The only thing they got wrong was where I said I was 'shocked'. I'm not shocked, I'm surprised, and disappointed by the quality of the code.
by jgrahamc 17y ago
The only thing they got wrong was where I said I was 'shocked'. I'm not shocked, I'm surprised, and disappointed by the quality of the code.
- tome 17y agoNo, I'm not shocked either. Mathematicians and scientists have no formal training in programming (at least in the UK). They're expected just to pick it up and get on with it. They don't generally put in the necessary hours like the "self taught programmer" does, because they're generally not interested in programming itself. It's just a calculational annoyance that gets in the way.
- Silhouette 17y ago> Mathematicians and scientists have no formal training in programming (at least in the UK). They're expected just to pick it up and get on with it. That's an unreasonable generalisation. For one thing, many university courses in science and mathematics do seem to incorporate basic programming training these days, either as part of the course, or via other facilities that the university makes available to those taking such courses. Any programming skills acquired may or may not contribute directly to the grade of degree awarded, but that is a different issue. For another thing, I can attest that some scientists do make an effort, because I have personally been paid by PhD students to tutor them in the appropriate programming techniques to implement their models soundly.
- tome 17y agoI'm talking from my experience of attending the most highly regarded mathematics undergraduate programme in the UK. There was basic programming training, but the emphasis was on the "basic". There was absolutely no emphasis placed on writing maintainable code. We (in fact "they": I didn't attend the classes) were simply taught some technical details of C. In fact I think the number of hours of teaching time was single figures. Now I can't speak for the engineers at the same university. As far as I know they were given excellent training in C++. But simply, the mathematicians did not take programming seriously, so I'm not surprised of the low quality of the implemented models.
- Silhouette 17y ago> I'm talking from my experience of attending the most highly regarded mathematics undergraduate programme in the UK. That's a bold claim. Which undergraduate programme would that be, and by whom is it the most highly regarded in the UK?
- pmjordan 17y agoI don't know which university the parent is referring to, but I can confirm that this was also the situation at the University of York, a top-10 UK university, at least at the time. (90%+ were people who hadn't quite made it into the top 2 - hence nicknames of "University of Dork" and "University of Oxford/Cambridge Rejects") The problem existed not only mathematics, where I ended up giving extra programming classes to friends because the teaching was practically non-existant. Also physics along with the computer simulation and theoretical branches of physics, which I happened to be studying. In fact, we were only taught rudimentary Fortran (!) syntax, and laughably, OpenMP and MPI later on. Nobody who made it through the course alive did so without having either learned to program earlier or investing a large amount of time in self-study and then "winging it" - after all, the final project depended on being able to deliver a simulation of whatever physical system was being investigated. I started programming when I was 10, so I had no trouble; together with a colleague who had a similar programming history as I, we introduced the rest of our year to basic good programming practices and workflows (split your functionality into stand-alone functions and files; use version control; avoid global variables; the merits of code reviews; etc.). A lot of people had already switched to experimental physics before we started doing this. Obviously, expecting people to understand concurrent programming at that level is pretty dangerous. In my experience, this sort of attitude breeds a view that computer programs are magical things, and once they compile and don't crash or hang, you can trust their results. This exact attitude is what I'm reminded of when I read about this CRU incident. I don't think any of the staff ever took the issue seriously, though. Even if they weren't prepared to teach it, they should have told everyone to teach themselves over the holidays and provide exercises or whatever. At no point did anyone point out that programming was a difficult craft, and that mastery of it would be expected. For context to those unfamiliar with the majority of UK science degree programmes: they are typically not as modular or flexible as in other countries. If you failed a module, you had one chance to re-sit the exam a few weeks later. There was no option of re-taking the module including lectures during the next term/semester; each term had a pre-assigned set of modules, there was no flexibility in when they could be taken, so you couldn't defer your concurrency project until you'd taken some more programming classes or so.
- jfischer 17y agoBeyond training in programming, scientists creating production code need training in software engineering. The folks over at Software Carpentry (http://software-carpentry.org/ http://software-carpentry.org/) seem to have the right idea. Just as important, like other forms of scientific experimentation, work based on computer analysis needs to be independently reproducable. A big part of that is to make the source code and data available to other researchers (ideally, to the public at large) and well-documented. It seems like the CRU people failed in both areas.
- Luyt 17y agoAnd this poor code leads to temperature data sets that could be flawed - data sets that form the foundation under the climate models and the conclusions of the IPCC reports. These reports in turn are used by many countries to base policy on. Are governments basing policy on flawed science?
- jodrellblank 17y agoI'd still prefer the (UK) government to be basing policy on flawed science than no science ( http://news.bbc.co.uk/1/hi/8334774.stm http://news.bbc.co.uk/1/hi/8334774.stm ).