A$200 per week for being on-call (5am-8:30am weekdays, 9am-5pm weekends and public holidays, three people in the rota). Actually having to do anything just goes into the normal overtime system.
For all the extra effort of having an on-call system it's used less than half a dozen times a year, but the boss likes being able to charge for it.
Problem is, there's a bad update combination for the RB1100 that can cause it to get into a reboot loop that has to be resolved in person with a direct connection and a recovery tool.
Why bother? The Venn diagram of people that need a bug-for-bug clone of RHEL and think that the proposed process is in any way appropriate is two seperate circles.
Two things spring to mind: My experience with a YouTube premium trial ended immediately upon being told that I couldn't play music in a second place at the same time. And ad-blocking is part of my security posture.
I have plenty of local storage. Moving forward, maybe good videos won't just go into a playlist with the assumption that YouTube will continue to be available.
Even while businesses promote government policy that looks to treat workers as rich and businesses as poor, they understand (as can be seen by lots of product pricing policies) that businesses are rich and individuals are poor. How many products have you seen with a cheap (or free) personal or family option, then expensive business or enterprise option? This is how the economy should be structured. Businesses should fund the government budgets and individuals should have lots of stuff (like public transport, or basic housing) provided free.
I nuked my Ubuntu Mate laptop and installed Qubes, just to get a feel for it. It's significantly more maintenance than a vanilla distro, because of all the separated environments, but if I ever wanted to return to Linux on the desktop as my main OS, I'd absolutely use it. It's the only BYOD/WFH solution I've found that feels even close to secure enough if you don't want to run physically separate PCs.
I work somewhere that specialises in secondhand enterprise equipment and storage. The answer to your first question is "yes, but they really shouldn't". We're burning more hours than we can spare dealing with drive failures. Sure, we have RAID arrays capable of withstanding multiple failures, but we still find ourselves scrambling to replace drives faster than they're failing, even when they were tested before they were put in the spare pile.
Also, fuck Chia. It was supposed to be a low-power "proof of storage", but it's really "proof of prior work" and burns even more energy than proof of work since you need to constantly power the cryptographic calculations AND storage.
Having recently attempted to move from LastPass to Bitwarden, only to have to abandon it due to sudden changes that broke third party integration without consultation or a sensible solution, I'd say this whole drama on brand.