Crashing and burning (in a non-production environment) is an excellent motivator to develop necessary skills; being unafraid to break things and fix them when they inevitably break helps you get a deeper understanding of how the systems work, for what it’s worth.
This appears to be a variation of the “standwich.” Please see the attached for an example.
Running an RKE cluster as VMs on my ceph+proxmox cluster. Using Rook and external ceph as my storage backend and loving it. I haven’t fully migrated all of my services, but thus far it’s working well enough for me!
Good bot
I don’t know how I feel about this personally. On the one hand, I feel like this is a privacy win for those who want it: no watch history means no algorithmic recommendations and (presumably) less data collection for those users. On the other hand, I personally really enjoy the recommendations that YouTube makes for me. Maybe it is the wide variety of content that I watch, but I’m honestly very pleased with the recommendations that YouTube provides. That being said, I feel like the opt-in to algorithmic recommendations is a good thing overall, however I am personally going to leave my watch history enabled.
Back when COVID was in its prime, I was contributing CPU/GPU cycles to Folding@Home for protein folding simulations and working on a vaccine. Since then, I’ve reimaged my desktop twice. I should probably reinstall the BOINC client to contribute again…
The Downtime Project is a pretty interesting podcast that covers some large outages and discusses their post-mortem analysises. Worth a listen IMO, very interesting stuff and some good lessons to learn.