To expand on the 3-2-1 rule for the uninitiated:
3 total copies
2 onsite, using dissimilar media
1 offsite, for disaster recovery
To expand on the 3-2-1 rule for the uninitiated:
3 total copies
2 onsite, using dissimilar media
1 offsite, for disaster recovery
We no longer have humor, it’s been beaten out of us by code reviews and merge conflicts.
I caught a junior trying to reimplement an existing feature, poorly, in a way that would have affected every other consumer of the software I’m a code owner on a week or two ago. There’s good reason to keep them around.
PRs suck to do, but having a rotating team of owners helps, and linting + auto formatting helps with a lot of the ticky tacky stuff.
Honestly, the worst part is “newGuy has requested your review on a PR you requested changes on but he hasn’t addressed” that’ll get you in the ignored pile real quick.
With enough grit and time, yes :D
Edit: ok not mainline, but Linux in some form or another anyway.
You can run a “soft” (semi-hard?) Processor on a Spartan, you could run Linux on that at least.
I’m moving to a few acres this weekend, assuming everything goes well. We got plans for a giant garden, a duck run, and fruit trees. This meme is all truth.
Being fully remote is a great gig if you can swing it.
I’m glad to hear this, I keep looking at it. I’m a little worried about the hardware requirements for it though. I keep putting off getting hardware for a dedicated jellyfin server (it’s on my wife’s gaming PC right now and it bugs the heck out of her)