onecheapgeek's Journal: How NOT to write a bug report

Info that could be used to identify this individual removed. I'm sure someone, somewhere can figure out how to find the info, but I won't help.

Fri Nov 02 19:39:46 2007: Request #### was acted upon.
Transaction: Ticket created by [e-mail]
              Queue: rt3
          Subject: Bug found: no documentation on REST interface
              Owner: Nobody
    Requestors: [e-mail]
            Status: new
  Ticket http://rt3.fsck.com//Ticket/Display.html?id=#%23%23%23
-------------------------------------------------------------------------
You idiots seemed to have left out the documentation for your REST
interface.

If all google can find in the way of manuals for your water head abortion
you call a ticketing system is a freakin MICROSOFT DOC FILE you know you've
sunk to new lows.
http://download.bestpractical.com/pub/rt/contrib/2.0/WebRT%2520Manual%2520-%2520User%2520Guide%2520share.doc
Wow guys, you rock! That's raising the bar all the way up to "polished
turd" level! Grats!

I work for a very large social networking company and apparently pissed off
someone enough that I'm being punished by having to figure out how to use
your "software." You guys really make the case for creating laws that ban
certain people from ever touching a keyboard. Like you, I agree that
punishment of this degree continues cruel and unusual punishment, but
whatever.

Take that how you will, your site sucks, your software sucks, and your more
then welcome to blast off on me all you want. It's not going to change the
fact that you apes are the fungal infection on the ball sack of humanity.

Have a great fucking day!

-- Xxxxxxxxx