Today @Delta both:
(a) made me remove the p100 I was wearing underneath my valve-less cloth mask;
(b) let people around me wear masks under chins for hours 🤦♂️
So I was surrounded by maskless people + had a much less safe mask myself. 0/10 idiotic safety theater, fly elsewhere.
(Why try a p100? Based on a microcovid.org rec—it's easier to get a good seal with a P100 respirator than an N95, and they are better filters. The cloth mask protected others from outflow. But, silly me to do something that needed *thinking* to verify it was ok.)
Classic case of rules based on socially-approved talismans rather than effects on reality: 1. As I pointed out at the time, (their interpretation of) the policy was instructing me to *just remove* a layer of protection and this couldn't possibly make anyone safer.
(This seemed to trigger a glitch in the conversational logic of the person I was talking with; he stopped trying to respond to anything I was saying and just started repeating variants of "you need to get a different mask" and "if it has a valve, it's not allowed" over and over.)
(Attempted steelman of this behavior: perhaps most people who wear a funny-looking mask are indeed wearing an unsafe mask, but are still able to out-argue the flight attendant, so the "glitch" is actually the safety-optimizing response on average?)
2. There was clearly selective enforcement based on the fact that me wearing P100 + normal mask looked weird, whereas all the people with masks under their chins were behaving socially normally (even though much more dangerously).
FWIW, United at least states that they allow this, so maybe a better option for non-socially-normal mask behavior? (Of course who knows whether flight crews will actually apply the rule correctly.)
When I was deciding on colleges, the top tier all seemed kinda the same, so I picked the picked the cheapest one.
In retrospect I think one of the biggest differences between them was actually housing policy
The details vary a lot and have a surprisingly big effect...
Harvard sophomores get randomly assigned to an upperclass dorm but can "block" with a group of up to 8. Dorms are small enough that blockmates will prob be your roommates for the next 3y. So after ~4mo on campus you basically guess at (+ audition for!) your "college friend group"
For some reason, while applying, this did not strike me as an obviously terrible idea, or at least not "could substantially affect outcomes" level terrible. It was though. A single decision, w/ limited info + lots of politics, basically determines your college friend group.
As a Kube noob who's been cut by a few sharp edges, this type of battle report was super useful to me :) Some stuff I learned:
Their backend is a monolith but they route different collections of endpoints to different nodepools—this is a clever way I'd never thought about to limit the blast radius of performance issues (not Kube specific either, and may be a common practice I'd just never heard of!)
GKE regional clusters incur big bandwidth charges for cross-AZ traffic; you can avoid by using multiple zonal clusters
TBH it doesn't look *that* awful from the chart—the egress it shows costs <=5k/mo and I'd guess Git storage is near-pathological for this—but useful warning
Most of my favorite writers are *way* funnier than me. Poeple gravitate more towards "fun to read" (vs e.g. "insightful") than we realize or admit!
Also, it's easier to make more jokes than to have better insights :)
Maybe people don't do this bc it feels manipulative? I disagree: reading is hard and boring. When you add jokes to a dry post, you're not tricking people into reading it instead of something more insightful; you're saving them from closing the tab and checking Twitter again.
A lot of people want to become a better programmer by learning things. But collectively we seem bad at routing towards useful subjects. Data structures? Compilers? Scheme? Math? Sure, they help a bit, but meh.
What scores highest on cost/benefit for becoming a better programmer?
A few of my answers (these may be idiosyncratic to Wave):
• Networking: helps understand an enormous number of things that I'd otherwise have to treat as magical mysteries
• Databases: these outsource a huge amount of complexity, so important to understand how they work
• Object-relational mapping: same rationale as databases, except you have to fight with them more often
• Obscure details of whatever language I'm using: it's just really useful to be able to easily answer "what is this code doing" in as much detail as you know
This week vindicated my "all infrastructure config is code that lives in a Git repo" paranoia more quickly than I ever expected 😬
Someone hit "delete project" in Firebase, expecting to delete a test app; turns out this actually deletes the GCP project, i.e. prod. (WTF WTF WTF)
(And no, the "are you sure?" confirmation modal did not clarify this at all.)
Fortunately "delete" actually means "shut down all instances + schedule data deletion for tomorrow," so we could immediately notice and turn things back on.
We were mostly recovered within ~45 min (most of which was waiting for Kube clusters to boot back up). The 2 machines that took longer were exactly the ones where we'd messed with iptables by hand and never verified that they could be rebuilt from scratch.