A very enjoyable read thank you. I wonder how does it look when a programmer panics or chokes
From what I've seen (and felt!) one might be facing a really nasty bug which has caused a sudden crash in a production environment which is holding up many hundreds of very angry customers. Some yelling may have occurred. You know you should sit back and reason out what the problem might be (it worked before -- what's gone wrong?) but the rookie reflex is to start coding right away and to slap something -- ANYTHING!…
The Art of Failure (2000)
11–13 of 13 posts
Re: The Art of Failure (2000)
#12She was leading 4-1 and serving at 40-30, meaning that she was one point from winning the game Eh, what?
Tennis has very strange scoring. It's complicated to explain, but here goes: The first person to get 6 games wins the set.* The first person to win 4 rallies in a game wins that game.* During a game, if you have one point your score is "15," two points is "30" and three points is "40." When you get four points or win by two, then you win the game. *One must win by two.
Re: The Art of Failure (2000)
#13Earlier quoted context omitted.
Tennis has very strange scoring. It's complicated to explain, but here goes: The first person to get 6 games wins the set.* The first person to win 4 rallies in a game wins that game.* During a game, if you have one point your score is "15," two points is "30" and three points is "40." When you get four points or win by two, then you win the game. *One must win by two.
Oh, what a debacle! Even after being such a devout tennis buff, I have confused "game" with "match". Or maybe I just can't read :(.