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.
Other times I've documented something for the sole purpose of showing
how bad the design was. Once I traveled to my employer's Colorado and
spent a few days documenting an absurdly unwieldy installation
procedure because that was the only way to persuade product management
that it was too complicated for any customer to perform.
On Wed, Feb 26, 2014 at 9:47 AM, Tony Chung <tonyc -at- tonychung -dot- ca> wrote:
> Have you ever solved a documentation problem by recommending changes to the
> UI, the benefit being that documentation was no longer required?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: new website, content widgets, and an output that works on any screen.
