... people would be maimed by now!

Work has taken a serious degrading turn today, but all I can do is laugh at it while my associate Falloutboy seethes with rage. Take in account that when we get errors from when our boss, a reputed programmer, it is usually a screen shot with zero information. The screen shot doesn't include the exception or indication of what is broken. An example of attrocious communication: It took about five emails between the boss and myself to nail down what she was talking about. I know that not EVERYONE has twoish years of testing background in the guluags, but the common courtcey of one programmer to another you figure she would include: where she's at, what she was doing, and how it came about.

Here's some work item humor: "Missing backend stuff". Yeah, that's the title. My first was "that's what she said", the second was "I wish I was", and the third was "and how!"