Is technical writing a calling or a job? Recommended DMN Communications podcast
September 11th, 2007 | Posted in Recom. Podcasts, Technical Writing 10 Comments »
A
fter a five-month hiatus, Aaron and Scott at DMN Communications returned to the podcasting scene. In this Sep 9 podcast, they discuss whether technical writing is calling or just a job? By calling, they refer to treating tech writing as if you were destined to be a tech writer, as if it was a sacred duty you were compelled by almost a higher power to complete.
Some writers exhibit this tech-writing-as-calling attitude by writing lavish introductions about the tech writing document itself. If you find yourself being too copious in your description of what you’re writing, rather than focusing on the instructional content itself, you fall into the tech-writing-as-calling syndrome. In the end, Aaron and Scott say to take your job seriously, but don’t take yourself too seriously. Tech writing is only a job — a potentially lucrative job, and a rewarding job. But not a calling.
My Reaction
My reaction? I agree with their assessment, but it’s somewhat a sad observation about our careers. If technical writing is not a calling, why are we engaged in it? Shouldn’t we quit and become firemen or doctors or human rights activists (or whatever we dreamed of being)?
I think most will agree that we tech writers ended up in this profession as a second or third choice. I felt that I should go into the writing field — I wanted to be a nonfiction essayist writing for magazines. But as much as I enjoy creative writing, I can’t make a living at it (yet anyway). My three kids depend on me. I’d much rather make a comfortable salary than squeak by on carrots and top ramen, living a spartan, solitary life.
But there are facets of the tech writing job that I find occasionally inspiring. I am fascinated by technology. That’s what gets me excited about my job. And working closely with other project members. Plus I have a knack for bringing organization and clarity to complicated and scattered information. I like the rewarding feeling of creating a valuable, true document that makes a complicated interface or concept accessible. It’s like a puzzle to solve.
Even if we’re not following our true callings, most glamorous jobs turn out to be a bit boring anyway. Even prize-winning novelists approach their work as a job. They don’t always feel like writing, but they slug away at the keyboard nonetheless.
Final Thoughts
I’m so glad DMN returned to the podcasting scene. Thanks guys! You made my morning commute so much more enjoyable. Tech Writer Voices is coming back too. It’s been almost 3 months since I published a podcast. But this morning I finally found my wireless FM transmitter (I temporarily lost it), and listening to my favorite podcasts renewed my enthusiasm.
Related Posts
- Three Excellent Podcasts on Networking, Outsourcing, and DITA
- Special DMN Communications Podcast with Tech Writer Voices (me): Are you Hurting Your Career By Not Blogging or Podcasting?
- Examples of companies integrating podcasts into their mix of technical communication deliverables?
- Recommended Podcast: Alistair Christie’s IT Author Podcast
- Intro to Information Architecture — Reflections on the Different Roles We Can Play
Tags: boring, DMN Communications, jobs, Tech Writer Voices, vocations
Twitter
iTunes














Tom,
Thanks for tuning in. Glad to hear that you’re settling in after your move — and Aaron and I thought we’ve been busy!
Anyway, keep listening. We’re hoping to get back and stay on track with the podcast.
Scott
I agree as well, it is not a vocation, just a job.
Admittedly that job can be exciting, challenging and lead you to be truly passionate about what you do, but, it’s not something that you do for any other reason than that you get paid for it.
That’s no bad thing of course..
You mean you wouldn’t just do it… for fun? You don’t buy a new piece of technology and edit the manual that came with it?
I agree that for most of us, tech writing is not a calling, but I disagree that that has anything to do with writing lavish, self-serving introductions to the document.
That’s not tech-writing-as-calling syndrome; it’s Rodney-Dangerfield syndrome. A writer who does that is trying to get more respect by explaining what they do instead of just doing it. I don’t see many people with “callings”, such as ministers, doctors, or fire fighters, explaining why their work is inspired or professional — they just do it. If it’s a calling, it’s a reward in itself, and you don’t need to seek anyone’s appreciation.
I like your term — “Rodney-Dangerfield syndrome.”
[...] Is technical writing a calling or a job? Recommended DMN Communications podcast [...]
[...] Is technical writing a calling or a job? Recommended DMN Communications podcast [...]
Great posting. Its really good post and informative information you provide.. Thanks!
That’s pretty cool
A writer who does that is trying to get more respect by explaining what they do instead of just doing it. I don’t see many people with “callings”, such as ministers, doctors, or fire fighters, explaining why their work is inspired or professional — they just do it. If it’s a calling, it’s a reward in itself, and you don’t need to seek anyone’s appreciation
Jade Borg
http://www.gpjobsaustralia.com/
Your explanation is nice.
This site gives a list of jobs
http://www.paidonline.we.bs