Perhaps it's the feel of a keyboard under our fingers, or the promise of a blank document window. Or maybe it's the unstoppable urge to explain things in the most elegant manner possible.
I've always wondered why we become technical writers.
There is that starving novelist vs. comfortably-employed techie aspect to consider. When you walk out of college with an English degree, a nice salary and the prestige of a high-tech industry can be hard to turn down.
But I think it runs deeper than necessity. In fact, I think many people are technical writers by nature even if they are stuck in other careers. They just don't realize it yet.
These people are easy to spot. Just stand in front of them and explain something in a confusing way. A dormant tech writer will start to squirm as they fight the urge to clarify your poorly-constructed explanation.
I'm a technical writer because I'm a technical writer. Circular reasoning? Yes. But it's true, just as a rose is a rose is a rose.
It's a fundamental fact of my existence.
So, why did you become a technical writer?
If you enjoyed this post, you might also like How to become a technical writer.
21 comments:
Twice in my career, in two completely different organizations, I was hired to do creative video / multimedia work, and then that work dried up BUT they needed some form of tech writing, so it was switch to tech writing or look for a new job. So I guess the major reason I'm in tech writing is job security. :-)
I actively pursued a technical writing career after a couple years working as a journalist.
The pay was better, the co-workers more friendly and easygoing, and the work just as interesting. Plus, I am able to see my wife and son now :-)
Technical writing is an awesome career, and I highly recommend it to anyone who can successfully juggle writing, technical concepts, and (occasionally) fussy clients.
In college, while pursuing a design degree, I worked as a tech support rep for a large income tax preparation company (rhymes with clock). After leaving that position, I became a software trainer with an independent software publisher. I went from trainer to technical writing (which is basically training without speaking) so that I could spend more time with my family. Technical writing just seemed like a natural transition from training. It has been a very rewarding career so far.
I'm a TW because I am a writer first, computer geek second. Simple as that.
I like playing with computers & software and writing about it. What other job will let me do that? Not many.
I wanted to become a technical writer since about 1983, when I realized I had a knack for it. Things didn't work out until December 2006. My career changed from computer programmer to technical writer in about three days. Opportunity knocked and I opened the door. I love it. I haven't looked back. I'm a bit of a geek and I enjoy writing. So I guess that is a good match.
Journalism didn't pay well, advertising truly was a rat race, and I enjoyed deconstructing devices. Where else would I go?
Wow, thanks for sharing all of your stories!
I became a technical writer because I can't leave computers alone; I'm entranced by the technology.
Add that to my love of books (dusty old computer manuals included) and the fact that I studied English in college, and the choice becomes obvious.
I became a technical writer because I was doing it anyway as part of my hardware/firmware engineering job. I probably was "born" to it: what else would the daughter of an engineer and an English professor be, anyway?
I discovered I had a knack for explaining things in concise language, and I enjoyed getting off the "critical path" of a project.
It's also provided me the opportunity to learn about diverse technical fields.
I fell into technical writing 22 years ago and haven't looked back since. I love what I do. I'm always learning and I get to play with things.
Not only that but I've had the privilege of working with some amazing people... engineers, programmers, marketing.
I can't imagine doing anything else for a living.
I found your message on Techwr-L, and I so enjoy hearing the stories of how people started their TW careers.
Me? I have been writing since I was a child. In college where I majored in Spanish and French, the Engineering Dept. offered a course in Technical Writing. I completed it with all As. When I approached my "prof" for her help in starting my TW career, she replied:
"You can't be a technical writer, you're a humanities major!"
I believed her. Although I lived in an area surrounded by IT companies and government contractors, I limped into financial services. Bosses noticed my writing talents. They helped me transition into writing policies and procedures. I transferred into various Training Departments and into Human Resources. The Training gigs involved writing print and online documentation for intranets, extranets, and Web-based applications.
To make a long story short, through blessings and being in the right place at the right time, I am now a very happy e-learning designer and developer.
I love what I do, although it took some time to get here.
One word of advice to career seekers looking into Technical Writing: follow your heart. Invite TWs out for lunch or dinner and interview them. Attend a local STC chapter meeting and ask the members about their jobs.
Stay away from the nay-sayers.
If what you read and hear about our profession gets your heart pumping, do everything you can to get your first TW job.
You'll be so glad you did, and you'll never look back.
Good luck!
I originally wanted to be an Architect. My high school English teacher suggested I persue writing instead. I didn't listen. I made it 3 semesters into architecture and decided it wasn't for me. I fell back on communication, and the rest is history.
In the post advertised at the bottom of the original above ("If you liked this post, try..."), the author says he's "dating himself."
Well, that is a lot of fun--but I enjoy dating others a lot more. ;-)
Most of my interests--except for dating--have always revolved in large part around communication. And whatta-you-know--even that requires good communication skills.
My writing, editing, tech writing, music reviews, songwriting (I learned guitar so I could create and play the music to the songs), exploring innovation, comedy, vocal impressions, creativity and communication...all relate to the urge to splash ideas around the universe--mine or those of others that I support or enjoy.
Do tech writers feel a need to correct inadequacies they see in others language? To explain the unexplained and sometimes unexplainable? To boldly write where no one has written before?
I think it's key in technical communication to enjoy writing, correcting what's already written, and teaching.
Are you a natural technical writer? Perhaps comedian and writer Steve Martin said it best:
"Some people have a way with words, and others...not...have...way?"
By the same token, some have a way with teaching and others--oh, dang it, just go learn it yourself! *%@#$*!#
I became a tech writer largely because it just suited me - kind of like what you're saying in your blog. It appeals to all parts of my being from the intellectual to the creative.
I taught tech writing at a couple of colleges and I explained it best by saying that I get to be Sir Arthur Conan Doyle for a living: I spend half my time as Sherlock Holmes following clues and unraveling mysteries, and half my time as Dr. Watson writing it all down for the elucidation of others.
And, ever since I read somewhere that tech writers are the only writers that don't reveal themselves in their work, well, I guess I like that part too.
I became a technical writer because I love words and gadgets. As a technical writer, I get to write about gadgets all day and get paid for it, too. [happy sigh]
There I was with a freshly-minted MA in 16th century drama and a desperate need for a job. Only two jobs listed in the newspaper (OK, it was a very long time ago) included writing in the title. Luckily, I answered the one for Technical Writer because it was listed before the one for Underwriter.
I fell into it. I'd gotten a degree in landscape architecture but didn't want to start working in the field at entry level pay. I was asked to proof a user's guide for a well-known desktop publishing program and the company liked my suggestions/edits so much, they offered me a job as a tech writer. I've never looked back. Turns out it's easy when you're good at it!
Tim, thanks for invoking the wisdom of Steve Martin in a technical writing discussion; I don't think that's ever been done before!
Dating myself? Yes...um... that didn't work out. I expected myself to be better looking, honestly, and man, was I peeved when I ordered the lobster!
Thanks, Craig. Nice original post to stimulate conversation!
One of the beauties of English is that it offers so many possibilities for puns, homophones, strange meanings, etc.--great fodder for humor.
Too bad you didn't find any English beauties on your date...unless your conversation was much more stimulating than I've imagined, or you look a lot better than I've imagined.
By the way, I hope you paid the check. Or did you have to pay for it?
Converting this into a one-liner:
The real trouble with dating yourself is that you always have to pay the check.
Technical writing tie-in:
This explores the technique of how I turned a cavalier comment, based on a quirk of English, into a one-liner.
I became a technical writer because I was secretary to a man who headed the Technical Information Department of a Dept of Defense Research Lab. He helped me sign up for a training program to get me out of a dead-end job (secy) and into a career. With the help of the gov't, I finished college and became an editorial assistant. I never looked back. My fist love is writing for science and engineering, but the jobs have brought me to IT. I am proud to be in a profession that makes technology more accessible to whomever needs it and I love what I do and the people who do it. Seeing all your comments warms my heart! Glad to be in your company.
"Because it makes me a better writer"
"It had me at hello"
:)
There aren't too many jobs out there where you are paid to continually learn new stuff! As one of the other commenters stated, "You got me at 'Hello!'"
Post a Comment