Comments on: Guest Post: Tech Writing Careers — The Raw, Unvarnished Truth http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/ The Latest Trends in Technical Communication Tue, 14 Feb 2012 08:22:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Is Your Technical Communication Career a Dead End? | Seek Omega http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-155004 Is Your Technical Communication Career a Dead End? | Seek Omega Sun, 04 Jul 2010 02:07:02 +0000 http://www.idratherbewriting.com/?p=2170#comment-155004 [...] less than engineering or a type of work that is more central to the company’s business.” Tom Johnson’s I’d Rather Be Writing (Guest Post by Keith [...] [...] less than engineering or a type of work that is more central to the company’s business.” Tom Johnson’s I’d Rather Be Writing (Guest Post by Keith [...]

]]> By: Is Your Technical Communication Career a Dead End? | CloudAve http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-153508 Is Your Technical Communication Career a Dead End? | CloudAve Tue, 08 Jun 2010 11:28:44 +0000 http://www.idratherbewriting.com/?p=2170#comment-153508 [...] less than engineering or a type of work that is more central to the company’s business.” Tom Johnson’s I’d Rather Be Writing (Guest Post by Keith [...] [...] less than engineering or a type of work that is more central to the company’s business.” Tom Johnson’s I’d Rather Be Writing (Guest Post by Keith [...]

]]> By: Tom Johnson http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-151108 Tom Johnson Tue, 11 May 2010 13:35:54 +0000 http://www.idratherbewriting.com/?p=2170#comment-151108 Michael, thanks for commenting on this thread. You pulled out two good nuggets from Keith posts, and I mostly agree with these points. I think that one can learn to enjoy technical writing, as simple and seemingly dull as it is sometimes painted out to be. Particularly, when you <a href="http://www.idratherbewriting.com/2010/04/01/comparing-creative-writing-with-technical-writing-2-min-videocast/" rel="nofollow">infuse story into the content creation for help topics</a>, it puts the whole endeavor in a new light. And as for the additional skills that go beyond writing, definitely pursue that as well. You should listen to my podcast <a href="http://www.idratherbewriting.com/2010/04/26/podcast-anyone-can-write-changing-roles-for-technical-communicators/" rel="nofollow">Anyone Can Write</a>. It's all about addressing that problem. Michael, thanks for commenting on this thread. You pulled out two good nuggets from Keith posts, and I mostly agree with these points. I think that one can learn to enjoy technical writing, as simple and seemingly dull as it is sometimes painted out to be. Particularly, when you infuse story into the content creation for help topics, it puts the whole endeavor in a new light.

And as for the additional skills that go beyond writing, definitely pursue that as well. You should listen to my podcast Anyone Can Write. It’s all about addressing that problem.

]]> By: Michaelfbp http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-150959 Michaelfbp Sat, 08 May 2010 15:50:31 +0000 http://www.idratherbewriting.com/?p=2170#comment-150959 The sheer durability of the topic on this blog speaks to what I believe is the heart of the matter, i.e., Keith Hood’s original comment that “If you want to make a life as a technical writer, you must sustain yourself by your enjoyment of writing, because you cannot get any satisfaction from your work any other way.” In other words, the central issue in this field of endeavor, as in any other, is to what extent its demands match your own propensities so you can get into the “zone” for optimum performance. Long, long ago I began to figure out that each of us represents a unique blend of inherited aptitudes and interests whose exact balance and nurture determines how we are “in the world.” For those of us who, for whatever reason, now face the necessity of reinventing their careers, the exploration process can be daunting yet invigorating. For that reason I’m especially thankful, now, to have stumbled across this conversation to help guide the effort. The second “nugget” I find in these posts describes an apparent professional trend toward greater fluency in the technical specialty for which one seeks to write. Perhaps, at least in terms of forthcoming opportunities to earn our keep, we should at least be grateful that demands for greater literacy are not being more widely imposed upon graduating “technoids.” The trend will definitely now guide my current efforts to acquire some academic creds in order to more effectively “walk the talk,” so to speak, among those with whom I will, in all likelihood, need to consult in order to get the job done. The sheer durability of the topic on this blog speaks to what I believe is the heart of the matter, i.e., Keith Hood’s original comment that “If you want to make a life as a technical writer, you must sustain yourself by your enjoyment of writing, because you cannot get any satisfaction from your work any other way.” In other words, the central issue in this field of endeavor, as in any other, is to what extent its demands match your own propensities so you can get into the “zone” for optimum performance. Long, long ago I began to figure out that each of us represents a unique blend of inherited aptitudes and interests whose exact balance and nurture determines how we are “in the world.” For those of us who, for whatever reason, now face the necessity of reinventing their careers, the exploration process can be daunting yet invigorating. For that reason I’m especially thankful, now, to have stumbled across this conversation to help guide the effort. The second “nugget” I find in these posts describes an apparent professional trend toward greater fluency in the technical specialty for which one seeks to write. Perhaps, at least in terms of forthcoming opportunities to earn our keep, we should at least be grateful that demands for greater literacy are not being more widely imposed upon graduating “technoids.” The trend will definitely now guide my current efforts to acquire some academic creds in order to more effectively “walk the talk,” so to speak, among those with whom I will, in all likelihood, need to consult in order to get the job done.

]]> By: Charso Bhis http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149827 Charso Bhis Thu, 15 Apr 2010 06:46:03 +0000 http://www.idratherbewriting.com/?p=2170#comment-149827 Mentioning that you are ISO 26514 complaint immediately earns respect from the engineers: http://www.scribd.com/doc/29262973/Technical-Writing-Standard Mentioning that you are ISO 26514 complaint immediately earns respect from the engineers:
http://www.scribd.com/doc/29262973/Technical-Writing-Standard

]]> By: Tom Johnson http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149822 Tom Johnson Thu, 15 Apr 2010 01:28:44 +0000 http://www.idratherbewriting.com/?p=2170#comment-149822 Kateryn, your comment is timely. I'm preparing a presentation about writers who play multiple roles. I'd love to hear you expand on why you find the smaller sized companies more interesting places to work. Can you expand a bit? Kateryn, your comment is timely. I’m preparing a presentation about writers who play multiple roles. I’d love to hear you expand on why you find the smaller sized companies more interesting places to work. Can you expand a bit?

]]> By: Katheryn http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149813 Katheryn Wed, 14 Apr 2010 17:21:16 +0000 http://www.idratherbewriting.com/?p=2170#comment-149813 I have been a technical writer for over 22 years. During the 1990s, at the time of the dot.com bubble, the field was exciting and challenging. Now, with the bust, technical writers often do nothing more than edit dreary procedures. I have found that working for small or medium-sized companies is much more exciting than working at a large corporation. I have also found that there are too many technical fields where the only qualification for writing is the ability to speak English. I have seen some abysmal writing and grammar lately... In the current state of the industry, I would NEVER recommend technical writing to anyone. If you want to write, find a niche where you are appreciated. I have been a technical writer for over 22 years. During the 1990s, at the time of the dot.com bubble, the field was exciting and challenging. Now, with the bust, technical writers often do nothing more than edit dreary procedures. I have found that working for small or medium-sized companies is much more exciting than working at a large corporation. I have also found that there are too many technical fields where the only qualification for writing is the ability to speak English. I have seen some abysmal writing and grammar lately…

In the current state of the industry, I would NEVER recommend technical writing to anyone. If you want to write, find a niche where you are appreciated.

]]> By: Tom Johnson http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149785 Tom Johnson Tue, 13 Apr 2010 04:03:57 +0000 http://www.idratherbewriting.com/?p=2170#comment-149785 Happylady, I'm intrigued by your comment. Can I interview you for a podcast about your experience in the tech writing career? Although your experience seemed to be negative, I think you have a lot of valuable lessons learned that you can share with others. Let me know if you're interested and I'll give you more details. Happylady, I’m intrigued by your comment. Can I interview you for a podcast about your experience in the tech writing career? Although your experience seemed to be negative, I think you have a lot of valuable lessons learned that you can share with others. Let me know if you’re interested and I’ll give you more details.

]]> By: Tom Johnson http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149651 Tom Johnson Wed, 07 Apr 2010 05:59:53 +0000 http://www.idratherbewriting.com/?p=2170#comment-149651 Scott, I agree with you. That post really shows the ugly side of the technical writing career -- one that I don't think is the norm. More and more companies are recognizing the importance of good user documentation. One support call alone costs about $28 at my organization. Not to mention that it deters users. I have been fortunate to be respected and valued in the companies where I've played a technical writing role. Perhaps it's a trend. Scott, I agree with you. That post really shows the ugly side of the technical writing career — one that I don’t think is the norm. More and more companies are recognizing the importance of good user documentation. One support call alone costs about $28 at my organization. Not to mention that it deters users. I have been fortunate to be respected and valued in the companies where I’ve played a technical writing role. Perhaps it’s a trend.

]]> By: Scott Baird http://idratherbewriting.com/2008/11/04/guest-post-the-dark-side-of-technical-writing/comment-page-1/#comment-149527 Scott Baird Thu, 01 Apr 2010 17:01:16 +0000 http://www.idratherbewriting.com/?p=2170#comment-149527 Wow, what a great post. It really bites deep, as evidenced by the firestorm of comments here. Although I agree with most of what was written and tend to think that those refuting the post's claims are wishful thinkers, I would also hope that moving into the second decade of this century tech companies are getting to the point where they do see the value of clear documentation. Social media and the rise in importance of the consumer's experience (versus just plain product quality) should point smart companies toward the fact that customers' experience will depend on how usable the product is, and documentation is big part of that. I currently work in Documentation for a great software company that's small-medium in size, and I have been blown away by how well documentation is treated here. We are part of the Development department and sit next to programmers and QA people. We are a part of every process, project, and design decision, and are respected and valued. It's incredible, I know, but true. I hope more companies follow this model in the future, because it's working very well. Support loves our manuals, as do the customers, and we are a better company for it. Wow, what a great post. It really bites deep, as evidenced by the firestorm of comments here. Although I agree with most of what was written and tend to think that those refuting the post’s claims are wishful thinkers, I would also hope that moving into the second decade of this century tech companies are getting to the point where they do see the value of clear documentation.

Social media and the rise in importance of the consumer’s experience (versus just plain product quality) should point smart companies toward the fact that customers’ experience will depend on how usable the product is, and documentation is big part of that.

I currently work in Documentation for a great software company that’s small-medium in size, and I have been blown away by how well documentation is treated here. We are part of the Development department and sit next to programmers and QA people. We are a part of every process, project, and design decision, and are respected and valued. It’s incredible, I know, but true.

I hope more companies follow this model in the future, because it’s working very well. Support loves our manuals, as do the customers, and we are a better company for it.

]]>