RE: "Managing Content as a Technical Writer "

Subject: RE: "Managing Content as a Technical Writer "
From: Erika Yanovich <ERIKA_y -at- rad -dot- com>
To: "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com>, 'techwr-l' <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 22 Apr 2014 08:46:50 +0000

For me, this falls in the nothing-new-under-the sun category.

<...content that is written, published, and then abandoned. Someone eventually comes around to it and wonders why it isn't working, and then they build something that does, and then it eventually gets abandoned as well.>

Even if you come up with a clever solution at one point, while learning new/cool technologies, you must have a maintenance process in place. It's much more fun to work on the migration project as a contractor and leave, than do the less fun but essential maintenance.

Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

"Managing Content as a Technical Writer ": From: Cardimon, Craig

Previous by Author: Word 7: Forms + Track Changes
Next by Author: Re: Google - how far do you go?
Previous by Thread: "Managing Content as a Technical Writer "
Next by Thread: Re: Anyone tried this in tech writing?

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

Sponsored Ads