I was pointing someone to the Amazon page for the book I co-wrote a little while back — iOS Apprentice, Eighth Edition — and I saw what you’re seeing in the screenshot above.
I like to think of my technical writing as sexy, but I didn’t think it was this sexy!
In case you’re curious, here’s what the actual cover looks like:
In all my years, I’ve failed it only once. But I’m certain that actually experiencing that failure ensured that the lesson would “stick.”
I happened a few years back. I was being diligent and getting all my tax stuff ready to send to my accountant in early February, around the time when my then-employer was sending employees their primary tax document, the dreaded Form W-2. (For those of you outside the U.S., it’s the wage and tax document provided by your employer; for example, the Canadian equivalent is the “T4 Slip”.)
I was doing a search through my company inbox to find the download location for my W-2 information, having forgotten that it was available through Workday. One of the search results was one of those phishing email tests, disguised to look like an official email with a link to my tax info. Since I was reading the email as search results and not as email, I was not in my usual email security mindset, clicked the link in the email, and boom:
I got the usual “Your manager will be notified and you’ll have to undergo mandatory security re-education” message afterward. Surprisingly, my manager never brought it up, and I was never scheduled for the “Don’t do it again, dumbass” remedial course, but believe me: I learned my lesson that day.
I get that for non-programmers to get the joke, the argument for setHealth() had to be the string "100%" and not the floating-point value 1.0, but Ars Heitiya’s comment made me laugh more than the original comic piece.
