Sometimes the workplace can be a little boring: Tester reports bug. Developer researches bug. Developer fixes bug. Repeat.

So the other day, I was researching an SCR and a particular foul one at that. In the SCR, I commented that whoever did this “should be tarred and feathered… hopefully it wasn’t me…” A little later, I received an email from the person doing the doc for the SCR saying that it cracked her up. Raymond Chen told an amusing story of poetry in a bug report:

I don’t know what overcame them, but the analysis was written in iambic pentameter… At any rate, the device driver team added one comment to the bug immediately upon receiving it: “We ain’t much fer book lernin’.”

So how do you keep it fresh and lively in the doldrums of bug tracking?