While many in our profession focus on the technical part, we believe that good writing is important, too. Here are some of our favourite posts on writing from 2010.
It’s that time of year again. We’re taking a much-needed break over the next couple of weeks to relax and recharge.
So, that means there won’t be any new posts in this space until January 3. That said, we’ll be highlighting some of our favourite posts from 2010 over the next week or so. Enjoy.
- Ellis Pratt asks where does your help sit on the technology adoption curve?
- Ben Minson on developing a list of standard tech comm products
- Is it about usability or changing user behaviour? I think we know the answer to that one …
- Kai Weber discusses efficiency and documentation
- Take a look at this use for Evernote: delivering documentation
Let’s take short stroll down memory lane. To 2007 to be exact. Back then, I was thinking a lot about wikis, writing about them, and using them fairly extensively. My thoughts then, as they are now, were about how to use wikis to write and deliver documentation.
For some reason or another, the thoughts and ideas that were floating around in my brain refused to coalesce into something concrete. Then came DocTrain UX 2007 in Vancouver. On day two of the conference I attended three sessions on wikis. The first of these was given by Alan J. Porter. That session gave my brain the kick it needed. All of the ideas and thoughts I mentioned started to come together.
Jump forward to 2010. I have in my hands a copy of Porter’s recently-published book WIKI: Grow Your Own for Fun and Profit. It’s a short book, but it packs a lot of information into its 150-odd pages. It’s easily the best book on wikis that I’ve read in a long time.
I don’t know why, but over the last few years the going rate for writers (technical and otherwise) has been declining. This has been something that’s been on my mind for a while now. It’s a tricky subject. That said, Aaron and I believe in charging what our work is worth.
As someone who has more than just a bit of experience and skill, I think that my time and my effort deserve reasonable compensation. I’m sure that the freelance technical writers who read this blog feel the same way.
And I agree with Canadian freelance writer Paul Lima who wrote:
I don’t give a hoot what the client expects to pay. I give a hoot about what I expect to earn.
One of the biggest problems that freelance technical writers face is what clients are willing to pay. As we’ve all seen, that can range from a decent wage to an insulting amount for a lot of work.