A useful rule of thumb for detecting bullshit: if you're dealing with a rule (principle, law) that comes in strong and weak versions, you're almost certainly dealing with bullshit. Examples: the strong and weak Efficient Market Hypothesis, the strong and weak Anthropic principle.
And the more versions there are, the greater the certainty.
A brief fun-time activity: find the perfectly spherical cow of uniform density in the sentence
"More circumstantial evidence that it's fine to hike and go to the beach, modulo some common sense."
Or we could argue a constant first derivative for the cost-benefit curve is jerry-rigged nonsense.
Momma Mia! That's-a some writing, eh!
Still in her apron, and standing nearly motionless beneath the archway that separates dining room from kitchen, she opens her mouth. Her voice builds and expands, reverberating. "Ave Maria" washes over the room, wine glasses vibrating, the song a presence itself.
J.M. Hirsch, Naples is Known for Its Pizza. We Went for the Meatballs.
Milk Street, January-February 2020
Are you smart enough to be a webdev? Probably not:
Absolutely not if you didn't view the source.
@MadestMadness I re-read the documentation and realized I'd forgotten that Emacs line wrapping is a disheartening combination of concepts, modes and config variables. Not even the simple, obvious, stupid thing to do (stick fill-paragraph in post-self-insert-hook) worked. Good luck on your journey.
The lesson Andrew learned was
Do not trust documentation blindly; it could be wrong.
which is ok. Another, more important lesson to learn is
Program defensively, make sure every case is handled. (The Elements of Programming Style, Kernighan and Plauger, McGraw-Hill, 1978).
A third, more obscure lesson available for learning is
Sometimes talking to the duck isn't enough, and you should talk to something that will talk back.
Andrew Tannenbaum, Lessons Learned from 30 Years of MINIX, Comm. ACM, March, 2016:
I mentioned [...] MINIX running on the simulator but not on the hardware to my student, [...] who said [...] the 8088 generated interrupt 15 when it got hot. [...] there was nothing in the 8088 documentation about that [...] I inserted code to catch interrupt 15. Within an hour I saw this message on the screen: "Hi. I am interrupt 15. [...]."
What lesson did Andrew learn? What lessons should he have learned?
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko