I’ve never had a negative experience contributing to open source.

I’ve also been to scrums where everyone is equal, and we have to be very PC, about explaining “processes” and “best practices” to people that break the build pipeline every single day. Eventually I just coded error handling and guard clauses into everything so no one could screw anything up by not following the documentation being a cowboy. That is a best practice, sure, but you’d be surprised by how people break things even after being warned not to do a very specific thing.

A cowboy that fixes things always 24/7 can be a maverick and talk shit.

But in todays PC world you can also be a cowboy that breaks everything always and spends weeks fixing something they themselves broke…

I wish I could say the things Linus said instead of just putting people on a performance improvement plan.

Sometimes being angry is appropriate. When I am I step back and try to figure out solution where the fuck up can’t happen again and no one gets hurt.

I’ve seen people be VERY angry and even hands on working in jobs where fucking up can kill people.

I’d rather see anger than people dying. Did Linus go too far here? Probably, but there is a time and place for anger and being direct.

Even a decade ago it usually meant ticking a box that you also allowed nonfree drivers.

Even Debian allowed you to download the specific nonfree driver you needed and add it (without Internet) at imaging so post install you could connect with wifi and not just Ethernet.

It’s come a long way. But doesn’t anyone else remember when windows did not have drivers and you’d constantly be confronted with “have disk”?

I mean, the amount of drivers for old hardware I still have saved… Because before win10 nothing would reliability always fetch the driver you need from the net…

Two tools worth using:

DMDE

Photorec

If the data is extremely important make a back up first.

Remember PhysX back when it was a separate
card Physics Processing Unit before they shoved it on the GPU before they even had multithreading? Yea it evolved. But the original implementation was not ideal.

It won’t matter that much UNLESS a specific setting you might want is disabled such as virtualization.

Consider checking now if virtualization is enabled or disabled. If your BIOS settings are fairly permissive it isn’t that big of a deal. But if they are restrictive it can make it a pain in the ass to work around.

Yea l knew someone that gave remote access out to one of these scams. Couldn’t be sure they didn’t leave a reverse shell so we just formated the drive and reinstalled windblows.