I work for Quest Software, makers of stuff like LiteSpeed, Toad, Spotlight, etc. My official job title is Subject Matter Expert, and one of my job duties is to blog. I think I'm the only paid-to-blog guy to answer so far, heh. Here goes:
How often do you write?
Usually only once a week, but I'll write several blog entries at once and schedule them in advance. I also do video podcasts, and the same schedule applies - I only do it a few times a month, but I'll record enough videos to release on a regular basis (every Monday and Thursday.)
I've heard from writers who block out a specific window every day to write. That doesn't work for me, and I've read blogs that sound like the writer said to himself, "I gotta write a blog today. Let's go crank one out, whatever it takes, no matter how much it hurts." It hurts to read those.
What do you write about?
Mostly about database administration in general. If you write about your own product continuously, you're not a blogger - you're a technical documentation writer. That stuff goes in press releases, not blogs.
Do you talk about competitor programs?
Only if they trash-talk ours, and I need to respond to clarify things. Otherwise, that's taboo. The products should speak for themselves.
Do you give away plans of new features that you are adding? Are you worried your competitors will read you blog and implement the features you are planning?
We patent significant new features, things that are really groundbreaking, so we're not allowed to talk about those until the patents clear. I'm currently writing a two-week series about the process of developing a new product and getting user feedback on it, but not about the specifics of the features.
How do you monitor who's reading your blog?
I don't - that sounds so Big Brother. I use Google Analytics and FeedBurner, but in the end, the only real statistics that matter are the users who tell your managers, "I read that guy's blog, and he does a great job of representing Quest to the public."
There's three types of readers:
- Your faithful readers who devour every post via RSS
- Drive-bys who find a specific post in Google and rarely visit again
- People who find a specific post via a link-sharing service like Digg or Reddit, and come in a mass crowd all at once - then rarely visit again
If you're worried about monitoring "who's reading your blog", you're going to be surprised - #1 makes up a very small percentage of readers. #2 is staggeringly large after you've built up a lot of content.
Do you have any idea about how many reads each blog entry gets?
Yes. Will I tell you? No, but your best bet is to use Google Pagerank. It's in the Google Toolbar. That'll help you compare one blog against another.
Do you get lots of comments? Are they helpful?
Yes, because it helps drive product direction.
Have any been severely critical of you?
Blog readers do a decent job of distinguishing the difference between people and products. If a product has a bug, they don't call me a moron. Every product has bugs. The fact that I'm a moron has nothing to do with it.
Is spam a problem with comments?
Just like it is with email. You have to protect yourself with things like Askimet and Captcha.
Do you think this helps your sales in any way?
Yes.
Can you attribute any sales directly to your blog?
Yes.
How much time does this take away from your programming.
Few programmers make good bloggers. Few bloggers make good programmers. If you really want to increase sales via blogging, or increase mindshare, don't bother your programmers - get marketing people. That's what they do.
Having said that, I'm a DBA and a former programmer. Sometimes it works.
Overall do you think it is worthwhile?
Absolutely. In the SQL Server software market, for example, all of the big players have community web sites, bloggers and experts. We all help interface with the community to make our products better. If you develop software in isolation from the community, you stand a higher chance of building software people won't want, or software people will have problems with. If you stay in closer touch with your end users, you get more feedback and build a better product.