It doesn't, a bad manager (allegedly) did. Having said that, having say 50% fewer commits than your peers is probably a reason to dive-deeper...it could be a good thing, maybe you were unblocking tasks and writing docs, or tackling the thorny issues...but also could be you are less productive.
I'm not sure that 55 months of up-time indicates it's more or less likely to go down in the next month, but I'd guess more likely.
Surely there are options, have you tried de-compiling the source from the binary?
>but the physical config was accidentally overwritten and there are no backups
Any old dev PCs lying around somewhere? It's worth reaching out to the old developers to see if they have a copy, in really old legacy systems it's fairly likely someone will have a copy somewhere.
I work at one of the other Big4 and to be honest it's not that impressive. This kind of report would be a high severity ticket, the person on-call for the given team would get paged, and wouldn't stop working/escalating until it got fixed.
Obviously not all companies behave this way, but they should!
I have a desire to be free. I'm working towards never having to look at a fucking computer again. Hopefully by the time I'm 30, I'll have enough to do only need to work about three months year. The rest of the time I'm going to be surfing or rock climbing.
I haven't read the article but Dr Ben Goldacre has written some great stuff on this. Incidentally he was the first person to get me engaged in science as a teenager, and I love his catchphrase: "I Think You'll Find It's a Bit More Complicated Than That".
We're in an industry ten years behind so we're just getting into Big Data. Obviously the issue that we can't write working normal software hasn't been addressed but we'll see how it goes. I'm actually relatively optimistic.
I guess they've decided it's better to show the correct forecast data + bad wind data than take down the page entirely.