when they're powered down.
There's no periodic cell refresh in flash memory like there is in DRAM. When USB sticks are plugged in, all you are doing is powering up the flash chip and interface ICs.
You'd have to read a block then write it back to actually refresh the stored charges in the cells.
I've commented on this previously, but this is essentially either a hit piece, or very poor reporting on Reuters' part.
Basically nobody looks at raw numbers for injury statistics. It's normalised to injures per million man hours worked, and when you take some conservative estimates on the size of SpaceX's workforce and the time periods involved, you find that they land pretty much in the middle of current "heavy industry" injury rates.
But it surrrre does look bad if you look at the raw numbers, just like if you looked at the combined raw numbers of, say, 10 steel mills across the country.
Permalink to my previous, much longer, comment
I don't think there's anything commercially available that can do it.
However, as an experiment, you could:
You could probably/eventually script this kind of operation if you have software that can automatically identify and group images.
Dammit now I have to reduce the block size of my discord-based cold storage filesystem.
They need to learn how to use their tools better. Winscp does all that transparently for you if you press F4 on a file on a remote system. Or maybe they did and you just didn't see it.....
It's quite a handy function when you're diving through endless layers of directories on a remote box looking for one config file amongst many.
Most times what I get when asking it coding questions is a half-baked response that has a logic error or five in it.
Once I query it about one of those errors it replies with, "You're right, X should be Y because of (technical reason Z). Here's the updated code that fixes it".
It will then give me some code that does actually work, but does dumb things, like recalculating complex but static values inside a loop. When I ask if there's any performance improvements it can do, suddenly it's full of helpful ways to improve the code that can make it run 10 to 100 times faster and fix those issues. Apparently if I want performant code, I have to explicitly ask for it.
For some things it will offer solutions that don't solve the issue that I raise, no matter how many different ways I phrase the issue and try and coax it towards a solution. At that point, it basically can't, and it gets bogged down to minor alterations that don't really achieve anything.
Sometimes when it hits that point I can say "start again, and use (this methodology)" and it will suddenly hit upon a solution that's workable.
So basically, right now it's good for regurgitating some statistically plausible information that can be further refined with a couple of good questions from your side.
Of course, for that to work you have to know the domain you're working in fairly well already otherwise you're shit out of luck.
If library devs do versioning correctly, and you pin to major versions like "1.*" instead of just the "anything goes" of "*", this should not happen.
Your unit tests should catch regressions, if you have enough unit tests. And of course you do, because we're all operating in the dream world of, "I am great and everyone else is shit".
If you're interested in the systems behind Apollo, go find and read "Digital Apollo".
It goes all the way through the project and describes in good detail everything, how they developed the control systems, the computer hardware, how the software was designed, how they implemented one of the first real computer systems project management, all the interactions between astronauts/test pilots who still wanted to "manually fly the lander", the political back and forth between competing teams, the whole thing.
It's a great read if you have a technical mindset.
They also came from a time when hard drives could draw several amps while in use and much more on spin-up. There was a good reason why SCSI drive arrays used to spin each disk up one-by-one.
Molex connectors are good for 10 amps or so, SATA connectors couldn't have handled that amount of current.
Excuse me, "UXers" is not the preferred term any more. You should be using "HXers", as per the article.
In my opinion, replacing "users" with "humans" feels wrong in much the same way as when incels replace "women" with "females".
They are reducing the accuracy of the description. All users of computers can generally be assumed to be human. All humans cannot generally be assumed to also be users.
Letting it ring has no impact. They have autodiallers that call, and when someone picks up, only then is that call assigned to someone in the call centre.
You can often tell this because there is a marked delay in the response to your initial "Hello?". Long enough that you can reliably just hang up if you don't hear a response in two seconds.
If it's a real person who actually wants to call you and they you call again straight away, you can just shrug off your hang-up as a network issue.
I've got photos in Flickr dating from 1999 onwards. Ten thousand or so of them, and a couple of the early ones are now corrupted.
But they are my "other backup" for Google photos so I don't mind too much. I also have a USB Blu-ray drive at home that I use to periodically burn M-Discs that I hand out to a few relatives.
That's about as good as I can conveniently do for backup, and it's probably better than the single-point-of-failure box of negatives that my parents have in their cupboard.