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.
Many of our customers would not accept a new product (be it HW or SW) without the docs.
Erika
-----Original Message-----
Gene Kim-Eng said:
> I have never worked on a HW project where documentation development
> ended up being the critical path to product release. Not that it's
> impossible, but you'd almost have to try to make it happen.
Or the customer could insist, which happens. Probably it's more common with brand-new, really large and very expensive hardware systems that no one wants to break on the first day.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com