Re: Calling a Bug a Bug

Subject: Re: Calling a Bug a Bug
From: sleepy -dot- me -at- verizon -dot- net
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 11 Mar 2003 20:03:20 -0700


That's where I am. "Oops!," "It broke," "Wow! Look at THAT!," "Now THAT'S
something I haven't seen before."

I work for a small company that puts out some heavy duty software. It can
be a rather odd place full of very driven and, often, strange people.

But we understand business also. Internally, we call a bug a "bug." To the
public, there is no such thing in OUR software. :-)


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Order RoboHelp Office X3 by March 14 and receive a $100 mail-in rebate,
plus FREE WebHelp Merge Module and FREE iMarkup Software, for a
total giveaway value of $439! Order today at http://www.ehelp.com/techwr-l

Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.



Previous by Author: Common approach to documentation
Next by Author: RE: 11X17 documentation
Previous by Thread: Re: Calling a Bug a Bug
Next by Thread: Documenting third-party software


What this post helpful? Share it with friends and colleagues:


Sponsored Ads