Apologies to anyone who’s been waiting for this post! Things have been much too busy for me with work. Hopefully I can get back to posting more frequently some time soon.
The first part of this series of posts (Why technical writing? #1) discussed why technical writers are needed. In this one, I’m going to talk about why someone might want to be a technical writer.
2. What makes a good technical writer?
I’ve been a technical writer/author/communicator for more than seven years now, and I’ve been passionate about my job pretty much from day one. After all, how many other careers would actually pay me for applying my inborn pedantry? I get to exercise my love of language and my love of technology in equal amounts, and it’s a job that I generally find fulfilling and interesting, even if it wouldn’t be everyone’s cup of tea.
Because of this, I’ve decided to write a series of posts about a job in technical writing is all about - this is just the first, and I’ll probably post weekly as long as I a) remember and b) have enough material.
1. So what do technical writers do, and why are they needed?
