One of the biggest strengths of switch statement, falling through to the next case, unless there's a break, is missing. Of course, I can't think of a good example right now, but I've used it.
Of course, I've also used switch statements in do { .. } while (false), so maybe I just need to be voted off the island.
It generates a ~10km route in my Canadian city that starts off in meters, and switches to miles. I know we're somewhat used to flipping between metric and imperial, but it's not a common thing to do mid-trip.
Coffee? That's not so bad. I'd be worried about it raining vomit. Its already bad enough when fluids start flowing along the floor, hitting the coats and smaller bags stowed below seats.
There was a dispute involving LTO-8 that just recently was resolved, so LTO-8 tape should now be available in the US. I wasn't following it closely, so I can't give any real insight, but it explains the wording.
Fortunately in Canada, we view busses as transport for the plebes. So when we finally brought LRT service up (a bit late) and the bus trip from home to work went from 45 minutes to an hour, my 15 minute driv was unaffected.
I probably grew up north-ish of you, but ticks were always a concern if you were in the bush. -40 in the winter wasn't enough to kill them off. Just figured it was normal.
For power users, it's not just the extensions on Android (though it's a big part). It's the massively cross-platform for many years: Windows, Linux, FreeBSD, Android, BB10, MacOS, and more (I'm only listing the ones I've used in somewhat recent memory). To have that feature parity across so many platforms has immense value to me. I can support family, friends, co-workers.
I think some of my pain came from attempts to unmount everything (particularly NFS) before letting long-running shutdowns (graphite/carbon) finished flushing, then never trying again. While diving into that and eventually coming up with a sufficient set of dependencies, I would fondly think back to the two (or more) phases of unmounting at shutdown that had that solved cold many years prior.
First thought - "that's just enabling bad budgeting"
But then I realized -- waiting a week, or two, or a month might be considered a loan to the business. Should you get a 2% annual interest for waiting to be paid? Or, because this is already the model everyone's been using for so long, does it not really matter? So now I don't even know where I stand on it.
I travel similarly equipped - with the idea that I can't lose (or lose control of) data I don't have with me. This addresses the threats represented by border control, intranational security checks, theft of device, and unintended hardware acceleration (@9.8m/s^2). At most, a laptop or a phone is a cache of data that's already elsewhere.
Case insensitivity for files in a unix-ish environment seems like a great idea, until you're searching PATH for an executable called "head", and both HEAD and head exist. Do you go for first match, or best match, falling back to case-insensitivity? Bonus points for the confusion that ensues when some of the file systems being checked are case sensitive and some are only case preserving.