Yoicks!

[billroper]

I saw a brief report on this in the Chicago Tribune yesterday, but it lacked the flavor of the post that I'm linking below.

Things not to say at GM when discussing product problems.

It is seldom that I get to laugh quite that hard, motivated in part by a complaint from one of our support folks suggesting that we not use the word "crashes" in one of our customer-facing documents describing a fixed bug in our product.

He suggested "has issues".

I counter-proposed "is automatically unloaded from memory".

We ended up with "can close unexpectedly".

*sigh* :)

Comments

[whl.livejournal.com]

At one place I worked, we had a function that reduced the resolution of an image (in real time). We, internally, called this decimation. (A fast google justifies this usage.)

As the manual went into production, our tech head tech writer requested we find a different way to describe the function, as decimation historically means killing one in ten. I forget if his main issue was that we weren't always dropping one of ten, or that he thought it was too violent.

[pheltzer.livejournal.com]

I assume you know that software never has bugs.... just undocumented features.