summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--_posts/2013-02-24-practical-joke.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/_posts/2013-02-24-practical-joke.md b/_posts/2013-02-24-practical-joke.md
index 709b5d7..15c2c1c 100644
--- a/_posts/2013-02-24-practical-joke.md
+++ b/_posts/2013-02-24-practical-joke.md
@@ -8,7 +8,7 @@ I've nothing exciting to write about so I'll share a prank I did a few years ago
To protect the innocent, I'll change all the names.
-I was working at a company named $LF. One of my colleague ($NG), always looks at his keyboard when he types. Some time he can type for a few minutes. Then he looks at his screen, only to realize that it's full or typo, or worse, that he had typed in the wrong window. This used to really bother me, because I know he's been typing for years, but I was not sure if he was looking at his keyboard because he needs to, or just because his head is too heavy to look at the screen.
+I was working at a company named $LF. One of my colleague ($NG), always looks at his keyboard when he types. Some time he can type for a few minutes. Then he looks at his screen, only to realize that it's full of typo, or worse, that he had typed in the wrong window. This used to really bother me, because I know he's been typing for years, but I was not sure if he was looking at his keyboard because he needs to, or just because his head is too heavy to look at the screen.
So one day, while everybody (except $GM) were away taking a break, I decided to conduct an experiment.
@@ -19,10 +19,12 @@ When he came back from the break, he starts typing as usual. Quickly he realize
* verify that the content of ``xmodmaprc`` was correct, and then tweak it
* reinitialize the layout with ``setxkbmap``
* use a tool (maybe ``showkey`` ?) to see what was the actual code send from the keyboard while hitting the key
+* probably recompiled a bunch of stuff
+* definitely upgraded his Linux distribution
At this point, he understood that when hitting *x*, *w* was received, and for *w*, *x*. He rebooted his laptop (because when in doubt, you should "[tried turning it off and on again](http://www.youtube.com/watch?v=nn2FB1P_Mn8)"). But the problem was still there.
-If I remember correctly, that's when he decided to look at the laptop's keyboard and tried to use it, only to realize that it was working correctly! That's when he asked the ops guy, $GM, who was sitting next to me, if there was a spare keyboard somewhere. I slowly turned my head toward $GM, whispering 'noooo' to him, and replied to $NG that, "nop, sorry, no spare keyboard, <insert stupid excuse #49>".
+If I remember correctly, that's when he decided to look at the laptop's keyboard and tried to use it, only to realize that it was working correctly! So he asked the ops guy, $GM, who was sitting next to me, if there was a spare keyboard somewhere. I slowly turned my head toward $GM, whispering 'noooo' to him, and he replied to $NG "nop, sorry, no spare keyboard, <insert stupid excuse #49>".
The other developers started to realize that something was wrong with $NG, but no one said or did anything yet. We were about 30 minutes in the experiment now.