Why is most of the substance of this post giant block quote links to his own Twitter? Clicking through to those is painful; it’s not like the author can’t afford to host some screenshots on his own domain.
Look up that case. The victim suffered third-degree burns and required skin grafts. The myth that it’s a ridiculous, over-litigious case is just that: a myth. The coffee was absolutely too hot.
I've been subscribed to this for years, and it brings me joy every time an astronomical event pops up in my notifications. Big thanks to the author, Canton Becker, who clearly does this out of a passion for remembering to look up.
As someone with just a touch of classical knowledge from high school band and such, I’ve truly enjoyed and learned a lot from the Classical Classroom podcast (https://classicalclassroomshow.com/).
I truly do not understand why this problem has gone on for so long. It's clear that many people think `.home.arpa` is ugly. It boggles my mind that the IETF and ICANN can't come up with some agreement to get `.home` or something similar codified like RFC 7788 tried to do. This just seems like a fight between giant bureaucracies while meanwhile the users suffer and bad decisions like assigning `.dev` are made. I get that there are rules around this sort of critical infrastructure and its management, but come ON. /rant
With the rant ended: can anyone explain to me why all the relevant organizations can't get together and assign a TLD for this purpose that doesn't end in `.arpa`?
Just this week in Pittsburgh, I saw an official corporate poster up in a McDonald's advertising a "competitive starting wage" with an 8.5″x11″ sheet taped to it reading "STARTING RATE UP TO 10$/HR." I doubt they'll have much luck at ≤$10/hour. Sure, it's more than the minimum ($7.25/hour), but the "up to" weasel words don't give me confidence.
In Rust, the signature of the function would be along the lines of `-> Result<whatever, Error>` and you'd have no choice but to handle the Error case of the Result or to panic. Either way, not a segfault.
Keybase uses a concrete image of a hamburger[1] for their "etc." menu, which I assume is a nod to this name. It made me chuckle when it clicked for me.
I see what you did there, I think. It’s interesting: I don’t mind capitalization and the a/an substitution here, although I could see the capitalization being confusing in another context. However, it’s/its and to/too almost always take me out of the flow of the text and force me to read it again to figure out the proper meaning. As a native speaker, I would still say I forgive the mistakes, but they do undoubtedly hurt my comprehension of whatever I’m reading.
I use fish as my main shell. Sometimes I find its documentation a bit obtuse, but I love the sense of humor in its tag line: “a shell for the 90s.” It was first released in 2005.
Just to help others searching for "confused lieutenant," I believe it's usually known as the "confused deputy problem," perhaps as a reference to Barney Fife. I do like the image of a confused lieutenant though.
I had a friend in college named jane smith, capitalized as so—that is, not capitalized. She always entered it this way and it always appeared to be correct until the next nightly database cleaning job ran and gave her initial capitals. Eventually the registrar told her that nothing could be done but that a note was made in her file to ensure her diploma was printed properly. Of course it wasn’t, but they did re-print it free of charge without complaint.
If you hold down Alt/Option on the Fastmail security page you can enable 2FA without a phone number. Their helpful support person cautioned me to not lose my 2FA device or recovery codes :)
