Twitter (and microblogging in general) is one of those activities that’s really polarizing. Legions of people love it — it’s blogging, with immediacy. Others despise it — it’s trivial and narcissistic, and just adds the the static of the Internet.
I sit somewhere in between. While I’m a fairly active microblogger, I tend to focus more on sharing information than telling people what I’m up to. Let’s face it, no one cares that I’m about to make some muffins for my daughter …
Still, many individuals and companies have used and do use Twitter as part of their business. Some use it for networking. Others use it for product announcements, to generate buzz, or to promote a blog post or speaking gig. Actually, there are a lot of ways that businesses can use Twitter.
That’s where this article (and this one) come in. They offer a total of 54 ideas that your company — even if it’s a company of one or two — can use Twitter for business. They even got a microblogging skeptic like me thinking!
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.