Hmm. Interesting extension. But for me, not being a heavy Youtube consumer, think I prefer to see the original title and clickbait thumbnail so I can avoid the over-the-top clickbaity stuff easier and not waste my time or give them bastards a view.

Well, I did not expect this.

Ave Caesar! We attack at midnight.

Yo, why no love for md5?

Turris Omnia. Powerful hardware, auto updates, config backup / restore (with anti-bricking feature), SIM slot, etc

Generally, you aren’t allowed by law an official managing position without a college degree, that’s true. But that would reflect on the job title, not pay or benefits. In my company, if you’re good, you’ll be acknowledged.

Depends on the field. For example, in IT, competence can be tested. Especially when a large percent of job positions aren’t filled with people that got a degree in that field. I have dev colleagues with psychology degrees and whatnot and one that only finished highschool, that are better programmers than others I know that do have an IT college degree. Good programmers are hard to come by, and the main aspect that makes you one isn’t a college degree at all.

And do you really need college too, to learn how to learn?

My point is, I have programmer colleagues that have a psychology degree or none at all. Do you think that they “learned how to learn” programming in college? No, they are good programmers because that is their passion. Learning doesn’t have a single recipe.

I sometimes interview what could be people that will write code in my team. The college part in their resumes has zero importance to me, and I’d argue that it should be the norm. If we’d do the “college degree mandatory” when posting a job offer, like many companies idiotically do, we’d lose a lot of good candidates just because they wouldn’t be able to apply.

Well, and it’s stupid. Plenty of people without a college degree stay for years and grow in the same company.

Excuse my ignorance, I don’t know much about 3D printer material types / filament resistance, but from a few 3D printed cases for small devices I had, isn’t the plastic brittle? Or the joints of layers. Especially for a long cylinder shape where force is going to be applied to. I dropped 2 cases on the floor and they broke in multiple pieces where 2 layers of filament joined. But granted, their thickness was 2-3 millimeters.

Is it just 2 Mw or is the article wrong?

As someone reading this thread, I’m stuck in an endless loop.

Holy shit, I stand corrected, those graphs speak for themselves. Bookmarked for future stats.

LE: Well, there’s also the section about average age of failure in their newest report: 2 years and 7 months for HDDs, 14 months for SSDs.

True, but it depends from person to person and it counts if you have a small or big drive, how often you watch and rotate your media, how large the media is. If you only have a 1TB SSD, and often download and watch blue-ray quality, 20 movies will fill it. It won’t be long until the same blocks get erased, no matter how much the SSDs firmware tries to spread the usage and avoid reusing the same blocks.

Anyway, my point is, aside from noise and lower power consumption advantages, I wouldn’t use SSDs for a NAS, I regard them as consumables. Speed isn’t really an issue in HDDs.

I use Hard Disk Sentinel, it’s not free, but it also monitors drives in Windows so you have an early warning at the first sign of issues. Also logs historic data (writes, temperature, etc) and displays them as graphs.

Failure rates for sdd are better than hdd

I’m curious on where did you find this. Maybe they have lower DOA rates and decreased chances to fail in the first year, but SSDs have a limited usage lifetime / limited writes, so even if they don’t fail quickly, they wear out over time and at first they have degraded performance, but finally succumb in 5 years or less, even when lightly used (as in as OS drives).

To avoid DOA / first year issues with HDDs, just have the patience to fully scan them before using with a good disk testing app.

From my experience, SSDs are more prone to failure and have limited writes. They are ment for running the OS, databases for fast access, and games / apps. They are not ment for long time storage and frequent overwrites, like movies, which usually means download, delete and repeat which wears the memory quickly. One uses electric current to short memory cells and switch them from 0 to 1 and viceversa, the other uses a magnetic layer which supports a lot more overwrites on the same bit.

If keeping important data on them, I would use them only in a redundant RAID configuration and/or with frequent backups so I wouldn’t cry if one of them fails. And when they fail, there are no recovery options as with HDDs (even if very expensive, at least you have a chance).

I also wouldn’t touch used server SSDs, their lifetime is already shortened from the start. I had 3 Intel, enterprise-grade SSD changes in our company servers, each after about 3 years - they just wear out. For consumer / home SSDs the typical lifetime is 5 years, but that takes into account minor / “normal” usage, ie. if used as OS disks. And maybe power users could extend that with moving the swap/pagefile and temporary files (ie browser cache, logs, etc) on a spinning disk, but it defeats the purpose of having an SSD for speed in the first place.

If you have media (like movies) in mind, you’ll find sooner than later that you’ll need more space, and with HDDs the price per GB is lower than SSDs.

If you have no issue with 1. noise, 2. speed (any HDD is fast enough for movie playback and are decent for download), 3. concurrent access, or 4. physical shocks from transport, go with HDDs, even used ones.

My two, personal opinion cents.

Not to brag by any means, but english isn’t my first language I knew all of the above.

The rush on getting it working the first time is 👌

That’s so true, but what I think keeps us hooked in the game are the failures, the figuring out the "why"s.

Reading as a kid about virus analysis and how they work in a short column in a… newspaper. Yeah, they even listed full Windows Registry paths. Didn’t know what HKEY_LOCAL_MACHINE was, didn’t own a computer, only knew about some DOS commands, but I knew I wanted to be able to do that job and decompile stuff (whatever that ment) and see how it worked. Just like dismantling (and ultimately destroying) toys to see the inner workings.

After finally owning a computer and being bored by the few games I had on Windows 95, being limited to Notepad, Internet Explorer (without an internet connection yet; or was it Netscape Navigator?) and Paint (in which I sucked, lacking any artistic talent), when I learned that I can just type stuff in Notepad, I borrowed a book about “programming” in HTML. Then Pascal, the pinnacle being a simple XOR encryption program, with a god damn white on blue “windows” interface with buttons (a la Midnight Commander). Writing TRIVIA “scripts” for mIRC channels made us gods. Then Delphi naturally followed, making my own tool to track how many hours I’ve spent on dialup a month (yes, internet was very expensive) while listening to 80’s music on Winamp. Nothing was more interesting than that. Then got a job and out of a sudden started making my own money by writing Delphi code. Up until then I wasn’t really aware that my passion would also bring food on the table. The rest is history.

Programming in those days felt unreal. Felt like The Matrix. I knew that what I want to do for the rest of my life is look at text on a screen, hit CTRL+F9, see a crash, set some breakpoints, and ponder around the room or while taking a piss about what went wrong and how to solve it. I’m no Einstein, but I understood why science people dedicate their lifes to their work and disregard completely their social life.