Software engineering communication failures

[stephbg]

I'm developing a presentation for a software engineering risk management conference, and am thus seeking appalling, ambiguous, tortuous or otherwise bad examples of writing. Requirements, tech specs, user docs, use cases, test protocols, marketing info etc are all free game. If it's allegedly English and theoretically intended to convey information about software from Person A to Person B, I want to see it.

Feel free to disguise the source of your gibberish by replacing company names with "Widget Corp" or similar. After all, it's a small town :-)

Links to wacky tech quote sites or specific cartoons also appreciated. TIA

Comments

[leahcim.livejournal.com]

I hope you're already well aware of daily_wtf. :P

[stephbg.livejournal.com]

Not for ages, thanks.

[(Anonymous)]

Late to this. I found a great example on a humble grocery bag: http://cybertext.wordpress.com/2009/05/05/even-everyday-objects-need-clear-writing/

Have seen heaps of really bad ones, but no access to them :-(

--Rhonda