RE: New TECHWR-L Poll Question

[KMcLauchlan -at- chrysalis-its -dot- com]

Assuming an informal report is not sufficient (i.e., 
to save somebody some embarassment due to an official 
report), I document the error as it stands, and I 
report it as a bug. If it gets fixed before release, 
then I adapt my doc. 

I don't get to fix coding or design errors. While I'm 
able to tinker and (largely) to understand C and C++, 
I can't be sure that any tinkering I did would not 
break something else. I'm not one of the people whose 
job it is to code our software, so I'm not "legally" 
entitled to check it out and modify it, especially while 
others are working on it.  Besides, if I was tinkering 
with code, I would not be doing what I'm paid to do.

Also, changes to S/W or F/W are carefully organized 
between development and PV. It doesn't pay to disrupt 
the cycle.

/kevin



> -----Original Message-----

> What do you, a technical writer, USUALLY do when you 
> find UI errors in software you are documenting?
> 
> * Fix the errors yourself
> * Report the errors informally
> * Report the errors to management
> * Document the errors as they stand
> * Do nothing and see if they are fixed later
> * File a bug against the software
> * Other/none of the above

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
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.