Either "trigger" is a blacklisted word or your domain is on a list somewhere, because my company has this url blocked under the "weapons" category.
That's unfortunate.
> My goal here isn’t “what is 100% the most reliability-oriented way we can build things”, it’s more like “what is the 80% of reliability we can get for 20% of the effort while still enabling devs to go fast”
The author also points out that these bullet points will not apply to every unique situation.
If your goal is to allow devs to go fast at the cost of more hardened code, then yes, skipping code coverage is a major way to code faster. There are definitely times when it is appropriate to skip writing tests when the primary goal is to go fast.
It's difficult to answer your question without knowing your specific situation though.
How do you manage this expectation when working in an environment where part of the office is in the physical building and part is fully remote? When we were all in the office (pre-covid), anybody could walk to your desk to have a face to face conversations.
My manager warned us not to deprioritize IM/calls or it could be used to justify reducing remote privileges (since there isn't a good face to face walk-up equivalent when remote).
I personally hated when people walked up to my desk without messaging me first, and I view unsolicited video calls the same way.
> I am currently plugged into my monitor which is providing power + USB. I didn't have to try three times to plug it in.
Unrelated to the plug orientation, occasionally my laptop fails to properly connect to my monitor over USB C (providing both data and power) until I have plugged it in several times. The issue could be either the monitor, laptop, or cable. This is just anecdata, but it shows how USB C alone hasn't solved the problem where it doesn't just work the first time.
> Even on something like a QNAP (which can be compared to managed hosting) this can be hard. Flip the wrong switch and you expose something to the world. Missed a security update: your device is now vulnerable.
It doesn't even require actively flipping switches, but can be from not knowing a vulnerable feature was enabled by default. My QNAP got hit with ransomware because of a vulnerability in the cloud access software that I wasn't even using. I've since locked down all non-local traffic.