Solid write up. If anyone's interesting in knowing more about how probability _came to be_ 'regarded' as real, i highly recommend Ian Hacking's "The Taming of Chance".
Thought provoking in so many ways.
> I don't like it when we go off script, because it's hard to compare with previous candidates.
Wow. Meep, zorp, hire me. The beauty of this section of the interview (as someone who also has done countless of these numbing, repetitive 'script' interviews), that it allows for candidates to be tiny bit unrestrained. Go on, ask whatever you think is important. Or funny. Or something that can give you insight into this job you're tyna get into. That's the part where you can actually differentiate between robots who memorized answers (whatever answer they might be) and people who are actually interesting that YOU, and your team, would find pleasant to work with.
What a wild generalization. I skimmed the article, and I see his point in "Go was designed by people working at Google to make it easier to write Google-relevant software, in particular network-resident servers", but that doesn't mean Docker and Kubernetes (and other tools that enable communicating with/usage of cloud infrastructure) being written in Go made it become the de-facto standard, and especially not "the language of cloud infrastructure". What about ALL the other components NOT written in Go?
I started it couple of months ago, but couldn't get past the first few chapters. It was too dry for my taste. Even though she's a brilliant scientist (I'd recommend checking her classic The Limit to Growth), it seemed like the earlier resources about the topic are much better explained rather than the newer stuff.
Systems Thinking, mainly through reading Russell Ackoff's books. The Art of Problem Solving is good, Turning Learning Right Side Up is eye-opening (and definitely one of my favorite books lately) and currently reading Redesigning Society. Highly recommended.