I am not sure where y’all evolved, but you skipped a few thousand years and a whole bunch of sharpened sticks.

I am going to need your 50 point summary of those obvious points in the longest form possible by this afternoon so I can be completely convinced that I have already made up my mind in the correct way. Thanks.

I don’t get it. The key still gets declared, but it’s value is null. “name” in an empty object would return undefined, not null, correct?

(Yes, this joke whooshed, but I am curious now.)

ur

It was on old 3.5" drives a long time ago, before anything fancy was ever built into the drives. It was in a seriously rough working environment anyway, so we saw a lot of failed drives. If strange experiments didn’t work to get the things working, mainly for lulz, the next option was to see if a sledge hammer would fix the problem. Funny thing… that never worked either.

I used to take failed drives while they were powered on and kinda snap them really with a fast twisting motion in an attempt to get the arm to move or get the platters spinning.

It never worked.

Did you get bad sectors? Weird things can absolutely happen but having sectors marked as bad is on the exceptional side of weird.

Maybe? Bad cables are a thing, so it’s something to be aware of. USB latency, in rare cases, can cause problems but not so much in this application.

I haven’t looked into the exact ways that bad sectors are detected, but it probably hasn’t changed too much over the years. Needless to say, info here is just approximate.

However, marking a sector as bad generally happens at the firmware/controller level. I am guessing that a write is quickly followed by a verification, and if the controller sees an error, it will just remap that particular sector. If HDDs use any kind of parity checks per sector, a write test may not be needed.

Tools like CHKDSK likely step through each sector manually and perform read tests, or just tells the controller to perform whatever test it does on each sector.

OS level interference or bad cables are unlikely to cause the controller to mark a sector as bad, is my point. Now, if bad data gets written to disk because of a bad cable, the controller shouldn’t care. It just sees data and writes data. (That would be rare as well, but possible.)

What you will see is latency. USB can be magnitudes slower than SATA. Buffers and wait states are causing this because of the speed differences. This latency isn’t going to cause physical problems though.

My overall point is that there are several independent software and firmware layers that need to be completely broken for a SATA drive to erroneously mark a sector as bad due to a slow conversion cable. Sure, it could happen and that is why we have software that can attempt to repair bad sectors.

Tin the wire and the pin first and then touch the iron to them both quickly. They should stick fairly well without needing to add additional solder. Also, like someone else mentioned, flux can help quite a bit. (Maybe even a cupped soldering iron tip might be useful, depending on the situation.)

Learning how to solder SMD components will get you extremely familiar with how solder behaves at that scale. Let’s just say it’s significantly different than just doing basic wires and THT.

(Well, the solder doesn’t really act different, but at smaller scales it looks like it does.)

Well, that spider is in for a hell of a ride.

Absolutely! You just have to ditch those silly luxuries like food and shelter. You could even start working 80 hour weeks in hopes of getting passed over for that promotion again. Until then, you can just dream about how that extra $100 a month could possibly bring the total time down to 9,989 years.

If I remember correctly from the good ol’ days, promoted sites/ads kinda stopped after the first few pages and it skipped past most of the SEO crap.

But yeah, I forgot how aggressive Google is with ads and AI now, those bastards.

It’s actually a good change, IMHO. You can just click directly on page 10 for anything that might be related to your original search.

It’s been around for a while. It’s the fluff and the parlor tricks that need to die. AI has never been magic and it’s still a long way off before it’s actually intelligent.

There was a story a while ago about how these pictures were staged and designed to show the muskrat in the worst ways possible. It was basically super cheap publicity.

This post is an example of how these pictures propagate and keep that goat a household name.

This guy was the real killer. The new RMcD is just the cover story.

Ctrl z

Yeah, I would think memory as well due to the screen artifacts in that low res mode. (That depends on how x86 memory is mapped these days, I suppose.)

🥶

Mr. Peanut approved.