RE: When it is right to be wrong?

Subject: RE: When it is right to be wrong?
From: Marguerite Krupp <mkrupp -at- cisco -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 6 Feb 2002 14:05:39 -0500

I tend to side with the "something is better than nothing" advocates. If we
waited until the software was 100% bug-free, we'd still be on rev. 0.001.
Same goes with the software documentation.

Remember that in school, 90% correct is an "A" grade. At a certain point, as
the curve of correctness asymptotically approaches the limit of perfection,
it costs more and more to get smaller degrees of improvement. You've got to
let it go and go on to the next product. That doesn't mean you stop trying
to make things better. You just realize when to let go.

And if you wait too long to let go, you'll miss your market. You might get a
perfect product, but so what?

Marguerite

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Did you know you can get RoboHelp certified?
To learn how, visit http://www.ehelp.com/techwr. Be sure to also check out
our special pricing offers and promotions for RoboHelp 2002.

---
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: RE: Failure rate of backup tapes?
Next by Author: RE: % of Users Who Read Software Documentation
Previous by Thread: RE: When it is right to be wrong?
Next by Thread: RE: When it is right to be wrong?


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

Sponsored Ads


Sponsored Ads