3 ms·
Yay! A story about politics, programming, and climate science, all wrapped into one! It's like Christmas has come early here on HN. And the story just keeps ge
by DanielBMarkham 17y ago
Yay! A story about politics, programming, and climate science, all wrapped into one! It's like Christmas has come early here on HN.
And the story just keeps getting better and better, too. Lots of twists and turns.
So now we have code comments which are incendiary put ahead of, as it turn out, dead code. It's as if we found IRS code that had pieces in it like "This part makes sure all environmentalists get audited" but then the next part never runs. So it looks awful, but it does nothing.
So I guess that's the key for any kind of code analysis, right? What does it do? You run the code. Has anybody taken the raw input and ran the code to make sure this piece of code is currently representative of the code used at the time?
No wait -- we can't do that, can we? Because the data was lost/destroyed, right? So we have some version of some abstract pieces of code with incriminating comments in them that aren't being ran. On one hand, if you're looking for some kind of solid proof of scientists gone wild, you're never going to find it -- no matter how many times you add up nothing and nothing you'll get nothing -- because there are data and reproducibility problems that we can never resolve So it's always going to be he-said, she-said. On the other hand, that's been the problem with this issue all along -- data, models, and reproducibility. This case just brings it all out into the glorious sunshine for programmers like us to view.
Outstanding.
- deleted 17y ago[deleted]