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 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...