I felt like this post was begging for a clever ‘test’ embedded within it like those “msot poeple don’t notice letter rveersals” emails. However, I can’t think of a convincing way to hide something in an article.
When I ran more D&D games via play-by-post, I wrote long campaign outline posts to get players, and in order to encourage people to read them I’d embed sentences like “PM me with the word ‘chartreuse’ and start with 50 extra XP” in long paragraphs. Not hidden, but a reasonable filter for people who bothered to read the things. (A lot of players were repeat applicants and learned to look out for these sentences; it didn’t tend to catch newbies.)
I still do this when I write long requirements specifications at work, especially when they are supposedly being reviewed by people who I suspect will mostly just sign off on them unread.
Also, by the same token, that I write the most insanely boring D&D campaigns ever conceived by a human mind.
“OK, I implement requirement R1347-b in an Asian mobile deployment” (rolls dice) ”Oo, too bad. You encounter a previously undiscovered regulatory constraint that renders R1347-b moot. You fall through to R2218 and pick up an error condition.”
I felt like this post was begging for a clever ‘test’ embedded within it like those “msot poeple don’t notice letter rveersals” emails. However, I can’t think of a convincing way to hide something in an article.
When I ran more D&D games via play-by-post, I wrote long campaign outline posts to get players, and in order to encourage people to read them I’d embed sentences like “PM me with the word ‘chartreuse’ and start with 50 extra XP” in long paragraphs. Not hidden, but a reasonable filter for people who bothered to read the things. (A lot of players were repeat applicants and learned to look out for these sentences; it didn’t tend to catch newbies.)
I still do this when I write long requirements specifications at work, especially when they are supposedly being reviewed by people who I suspect will mostly just sign off on them unread.
So what you’re saying is that your co-workers have characters in your D&D games. :)
I suppose.
Also, by the same token, that I write the most insanely boring D&D campaigns ever conceived by a human mind.
“OK, I implement requirement R1347-b in an Asian mobile deployment” (rolls dice)
”Oo, too bad. You encounter a previously undiscovered regulatory constraint that renders R1347-b moot. You fall through to R2218 and pick up an error condition.”
Sounds more like a Paranoia game...