@steve milesworthy
As to the number of errors in Easterbook’s code, I am pretty relaxed. Because the real Numero Uno Problemo is that the models do not accurately predict/project/forecast the future climate. It doesn’t matter how many bugs are in the code if it still produces garbage.
I have asked you several times to produce the long list of triumphs of climate modelling that you have all been paid good money to produce. And every time you just produce a lot of irrelevancies and diversions. But precisely zero/zip/nada triumphs. After 30 years work, nothing of value has been produced.
My objection to Harry_Read_Me is simple. It shows that the general standard of IT ability in CRU is abyssmal. To even allow a dataset without a good description of what it is, where it came from. what the fields are, when we backed it up, who owns it and all the other stuff that made poor Harry’s life a misery into a data centre at all is pretty reprehensible.It does not speak well about the likely quality of any IT based (i.e all!) of the work of that department. If it has extremely sloppy processes for one piece of data, it is extremely unlikely that they have scrupulous processes for another. A houseproud person does not become a slattern overnight. Nor vice versa.
If the CRU sloppiness were just an isolated example, it might be overlooked or seen as a rogue bad apple in an otherwise ‘clean’ profession. But it doesn’t seem to be. Anybody with much professional IT experience is horrified by HRM. And many, like me, are happy to say so.
But AFAIK no climatologist has even turned a hair at what it shows. They are unconcerned about the amateurism and shoddiness it shows. I guess they just see it all as normal practice. Which reinforces my point.
‘You come across to me as a waterfall man whose only contribution to software development is to ensure that people write documents with the right titles and put them in the right coloured folders. I understand there were a lot of them around in the 70s’
‘
No idea what a ‘waterfall man’ is , so I’ll (as usual) assume that you are paying me a compliment. But my IT career didn’t really begin until early 1980 so I plead not guilty.
But if you mean that I believe that to do professional iT you need to get well-organised, approach your tasks in a logical fashion, adopt standard processes so that they become instinctive and exude a professional approach in all of it, then I plead 100% guilty. I’ve spent too many sleepless nights getting big and complex systems back on the road when some person or some combination of people have failed in one or more of these areas.
And I’m sure that you have followed the recent events at RBS with interest. A classic case of forgetting to get the basics of IT right. The code being executed may have been flawless, but it was working on the wrong thing and it seems a crucial control file was corrupted. And with widespread unhappy consequences.
I’d hope that ‘professional climatologists’ who all use IT as one of their very important tools would wish to apply the highest standards to that aspect of their work. Sadly it seems that they don’t even know they have got a problem, let alone be trying to fix it.