- Audience tweeting at conferences is increasing. Here are a few lessons on using Twitter as a participation tool
- The five sins of technical writing
- A brief post on brevity
- Interested in how Open Source projects get documented? Then take a look at the GNOME Handbook for Writing Software Documentation
- Where did all the documenation go?
- Something every technical writer knows: copy and paste is evil
Over the last week or so, the demons of the computing world have been swarming around me and making my life a bit difficult. Mostly, it’s been little things that have gone wrong. Annoying, but I could deal with them.
But, yet again, there have been a few error messages that have have left me shaking my head in disbelief. One offered a good chuckle, but the other two … well, in the immortal words of Richard Nixon huh?
Over the last while, I’ve had conversations with other technical communicators about using a wiki for documentation. Many have been interested and enthusiastic about the idea. Others, somewhat frigid.
But a question that a few of them asked was How do I get the documentation out of a wiki? My answer? Don’t worry about it.
Specifically, the focus of this blog. About a year ago, Aaron and I were chatting and he mentioned that he’d had lunch with a developer we’d both worked with at The Company That Shall Not Be Named. During lunch, the developer mentioned to Aaron that he’d taken a look at our blog, and that he couldn’t read it. Not because of the writing, but because of the subject matter — being a developer, tech comm wasn’t really interesting to him.
Fair enough. When this came up in our chat, it prompted Aaron to ask whether we were limiting the focus and scope of our blogging. The implication was that perhaps we should consider trying to gain a wider audience. We discussed that for a while, and never came to a conclusion about what to do.
- We’re not the only ones who think this: some people are crying out for good help
- Sarah Maddox discusses being part of a distributed team
- A manager’s guide to single sourcing
- Eddie VanArsdall takes an in-depth look at working with wikis — part 1 and part 2
- Twitter for usability testing and document testing? Anne Gentle explains how
- Here’s an idea: including recommendations in a user interface to enhance motivation
Yes, we succumbed to the siren song. Aaron’s been tweeting for a while, and Scott grudgingly did a Twitter experiment a while back. But a team Twitter feed? We figured why not give it a try …
But you can now follow us on Twitter here: http://twitter.com/dmnguys. We’ll be posting about tech comm, content, and related topics. While you shouldn’t expect us to be posting as frequently as Scott Abel, expect at least four or five tweets a day.