I was really hoping this would be a list of books you had decided not to read, with short (ideally flippant) justifications. Followed, inevitably, by passionate and erudite rebuttals.
I wrote a really long blog post about this once without the clock metaphor.
This is far superior in illustrating the slippery slope.
Aside from that slide too an inevitable dinner with Turing completeness, there's often the problem of sourcing information from multiple files overlaying it backtracking where it's sourced from.
Docker files are an example of this, as is the complete list of config values in spring framework (it's like 30 different sources).
In addition config starts getting into secured secrets, service invocations, database lookups, operating system commands, and who else knows what.
So not only is it really a touring complete problem, it veers into hellscape that is system integration.
Tom Kealey, one of the lecturers quoted extensively in this article, is a fantastic teacher. I took a class with him toward the beginning of his time at Stanford, and I often find myself thinking about what I learned. Tom took us seriously, those shy and strange kids who were just waking up to our own interior lives. He read our fan fiction, our intriguing premise that went nowhere, our characters who were always bursting into tears portentously, and he helped us learn how to stop copying what we had read, and to begin to find a voice.
The university statement says “However, we firmly believe that the changes advance the program’s pedagogical mission and provide promising writers with the resources to complete their books and obtain appointments at other colleges and universities.” I think that’s completely ridiculous. It will definitely do the second thing; how could it do the first? Promising writers preparing for publication have a great deal on their plate. Why would we expect them to excel in pedagogy because they write well?
I’m not surprised by this: IoT Hub is the core infrastructure piece powering Azure IoT, and it’s not going anywhere per the article. IoT Central, which is being phased out, was a layer on top of IoT Hub and other components that always had a somewhat awkward position. By trying to offer prepackaged IoT solutions, a lot of the power features were harder to use, but the solutions weren’t really end-user ready. Given the IoT hype dying down this makes sense.
Yes, that’s exactly the convention that C4 specifies: add legends on every diagram and make sure things are labeled in a way that people can understand.
Damn, I didn't realize I screwed up that message.
It was supposed to be
"Isn't bacillus cereus (the culprit in that case) the microbe associated with 'fried rice syndrome'? It seems to be pretty nasty, but also easily avoidable."
