not personally, i may have seen a video or two of it happening, but it’s hard to tell whether the head is dragging against the platter, or it’s the bearing, either one of those makes horrendous noise.

If you’re worried about it happening on a drive you own, you should copy that data somewhere else as a backup, ideally sooner rather than later. If you’re curious about the health of the drive you do stuff like SMART tests as well.

Yeah, most drives are solid state now, unless you’re buying hdds for archival purposes, still cheaper and denser in most cases. It’s a low probability failure, until the drive meets EOL, in which case it’s a mechanical wear part, either the motor or the bearing fails. One of them will fail first, probably the bearing.

The bearing failing would likely result in the HDD overheating as a result. Assuming the platter still spins, but that’s the only scenario i can think of where that would happen, unless you dump a very specific amount of continuous current into the read arm coils. That might also cause it, but it’s not likely at all.

An ssd “overheating” is more likely, but it shouldn’t cause too many issues, maybe premature degradation over long term use, and slowing of read/write speeds, or in some cases, an improvement, but other than that it should be business as normal. You would have to hit it with like a heat gun, to get a hardware failure or something like that.

I had it happen to a random hard drive I bought, old bastard found in a bin at a local thrift store. Anyways had a big dent in it and while it started up, even booting into windows XP it cooked itself made a screeching noise and was hot to the touch. Don’t think I need to explain that the big dent was probably the source of the overheating, anyways had to use an oven mitt to relocate it to a metal bucket of water where it boiled for a minute.

Removed by mod

Technical enough to be hired, is all I meant. 🙄

First year? That shit is like A+ cert level knowledge or below, and A+ is damn near worthless. They would know that in the first few hours of a study guide

CS departments were doing poorly, but now they’re putting out farmers? No wonder all these new graduates can’t find a job.

I’m not sure how well that analogy holds up. Farmers are usually pretty well versed in mechanical systems. To the point that now that John Deere has been screwing them over on right to repair that some farmers are even becoming versed in computer programming so they can flash the firmware on their tractors.

Just keep trying to justify your own lack of competency I guess. ¯\_(ツ)_/¯

A lot of farmers are learning how they work cause the companies that sell them the equipment keep fucking them over. I would argue that farmers nowadays needs to know how that works along with basic programming to get past the anti-consumer bullshit companies put in to make it nigh impossible to fix things yourself.

It is good for the programmer to know how the computer operates, as well.

You’ve never met a farmer in your life.

No, not really. Programming requires understanding of the underlying hardware, at least to a certain extent. Otherwise performance issues will look like dark magic and optimizing anything would be impossible.

Where do you start debugging if something goes wrong with the software and your information level is this low/ do you look at network stats? CPU utilization, paging/swapping? Is the hard disk bandwidth the bottleneck? Without at least some passable understanding of a computer architecture people like this just throw up their hands, or throw whatever tricks they know at the wall and see what sticks.

What the fuck

How is he going to fix his tractor? Wait days for John Deere to send somebody? Let the crop rot on the vine?

Horseshit. Computers aren’t tools for a software engineer. Computers are tools to an administrator, an accountant. Computers are the sandbox you are building castles in as a software engineer. If you don’t understand the system upon which you build, its abilities and features, its limitations, it’s dependencies, you are going to make some stupid mistakes.

You need to understand discrete mathematics as a consequence of computer computation. You need to understand parallel processing and threading for muli-core processors. You need to understand networking, package management, security vulnerabilities, etc. from different architectures and protocols. And it ALWAYS helps to understand the very basics of a computer’s functioning, from hardware, CPU architecture, machine code, assembly/low level programming, memory management, etc.

print('Hello, World!) is day one shit for a reason. Programming language and logic is the basics. The real expertise comes from your 3rd and 4th year materials. Databases, architecture, theory of computation, discrete mathematics, networking, operating systems, compilers, etc.

the only reason farmers are afloat financially is BECAUSE they can rebuild an engine if needed.

Just look at the john deere right to repair shit. It’s literally a huge problem.

I mean to be fair the sheer amount of material most university engineering programs require these days makes spending significant time on specific problems almost impossible. They try to shove so much theory into your head they lose track of practical implementation. Basically everyone I went to school with complained about the lack of practical application relative to theory, and I studied mechanical engineering which is theoretically and literally chiefly concerned with hardware.

Honestly that’s good to hear. I’ve run into some devs who are completely mystified on how to connect to a remote database and couldn’t tell a socket from sandwich.