Programmer Humor

Are you telling me there’s a difference between an inner and a cross join?

Cross join is obviously faster, I don’t even have to write “on”

When an HDD works continuously it can heat up to above 60 °C if proper air circulation is not allowed, which can cause a very premature failure. In fact, it should be kept under 40 °C to achieve the intended lifespan. Unfortunately, PC cases are usually not great at removing heat from the HDD by default.

As for your drive, it most likely has a temperature sensor so it can be displayed by various utilities.

it is, in the select event that your platter bearing fails, in which case it would be very, very obvious.

I'd much sooner assume that they're just fucking stupid and talking out of their ass tbh.

Even if it was local, a raspberry pi can handle a query that size.

Edit - honestly, it reeks of a knowledge level that calls the entire PC a "hard drive".

Have you ever heard of case of overheating hard drives within the last decade?

My one question would be "How?"

What the hell are you doing that your hard drives are overheating? How do you even know it's overheating as I'm like 90% certain hard drives (except NVMe if we're being liberal with the meaning of hard drive) don't even have temperature sensors?

The only conclusion I can come to is that everything he's saying is just bullshit.

You're giving this person a lot of credit. It's probably all in the same table and this idiot is probably doing something like a for-loop over an integer range (the length of the table) where it pulls the entire table down every iteration of the loop, dumps it to a local file, and then uses plain text search or some really bad regex's to find the data they're looking for.

60k is laughably, embarrassingly small. It's still sqlite-sized.

A TI-86 can query 60k rows without breaking a sweat.

If his hard drive overheated from that, he is doing something very wrong, very unhygienic, or both.

They make nothing. They're compensated for destroying things, and considering it's musk, they're likely given relatively little money in return for their time.

Even if the only thing you do all day is sit on the toilet and yell at the Internet, you're already a bigger net positive on society.

Even if querying data was processing-heavy and even if somehow the ‘hard drive’ got warm during this, then there still would need to be a hardware defect in order for the drive to overheat.

60k rows is generally very usable with even wide tables in row formats.

I’ve had pandas work with 1M plus rows with 100 columns in memory just fine.

After 1M rows move on to something better like Dask, polars, spark, or literally any DB.

The first thing I’d do with whatever data they’re running into issues with is rewrite it as partitioned and sorted parquet.