An American air-to-air missile modified for naval use, deployed on a land based Warsaw Pact launcher. Now that's something!
Three fries short of a Happy Meal.
This is getting out of hand!
So, basically this?
How much energy can it cost to replicate one coffee?
-- Janeway, probably
I don’t want to build car hell yet again
this, so much
Instead I'd probably take multiple measurements some hundred milliseconds apart and do a basic statistical analysis (average as "main result", but also lowest percentile, highest percentile and median). That way I don't feel dirty for tricking the customer.
STDs
Those Klingon look more like ST:D/s to me
spoiler
Seems like Surovikin is already in custody.
Even if Snowden could leave the country somehow, where to? Even in Afghanistan he would be just a drone strike away from heaven - not that they'd bewelcoming him either.
Aside: for a moment I confused with Sergei B. Korolev with Sergei Korolev, the famous Ukrainian rocket engineer.
4-5 times now. When confronted with more than a hundred commits between latest known working version and the one you've observed the bug (which was not catched by any of the unit tests) it can save some time to find the fishy commit.
In such a case I create a testcase on top to reproduce the bug. Then bisect and for each stage add the testcase, build, run tests. FYI: this only works if all (or at least most) of the commits in the chain are compilable - if you've done a big messy refactoring with several commits breaking the build, bisect can get you only so far.
First thing to do is check SMART data to see if there are any fails. Then looking at usage hours, spin ups, pre-fails / old-age to get a general idea how worn the drive is and for how long you could make use of it depending on risk acceptance.
If there are already several clusters relocated and multiple spin up fails, I'd probably return the drive.
Apart from all the reliability stuff: I'd check the content of the drive (with a safe machine) - if it wasn't wiped you might want to notify the previous owner, so she can change her passwords or notify customers about the leak (in compliance to local regulations) etc. - even if you don't exploit that data, the merchants/dealers in the chain might already have.
Just rewrite it with 80% functionality and force migrations on the users. Once the remaining 20% "edge cases" that require serious effort hop to the next job - where you where hired to "maintain" such a system and "just add a small feature here and there". Ooops.