TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
It's a new variable whenever it's not accounted for.
Yes, usually the process is at fault, but more times
than not documentation is outside the loop in this
regard. You can't argue against that... hell, that
complaint is posted here almost daily...
--- Phil Levy <PLevy -at- epion -dot- com> wrote:
> This is not a "new variable" it's someone's mistake
> in judgement. And this
> is not really typical. Usually it's the process
> itself that is at fault.
> -----Original Message-----
> Or being able to bend an entire process (if needed)
> fit a new variable, such as last minute product
> changes or custom tailored content for customer x.
Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
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.