I maintain a few blogs, well I maintain a personal one. The one here at SQLServerCentral.com doesn't get so much work, but I'm trying to get better at that. It's hard for me since this editorial is almost like a blog, so finding a whole separate set of things to write about, and then separate them from articles, is tough.
Lots of companies these days are looking to get their employees to blog, with various degrees of success. Some want the exposure, some want to show off, some think of it as another marketing channel, and some just do it because everyone else is.
However it's not that easy a thing to maintain for a company. I follow lots of blogs and I've seen so many die after a few months because people don't want to be bothered to write. I've got almost as many dead blogs to watch as I do live ones. Thank goodness for Google Reader to allow me to only see new items.
But allowing everyone to blog and express themselves doesn't always work out well. I saw this mention about Google and some employees that write something about the movie Sicko. I could see what the employee was trying to say, but it didn't sound good. And it makes you think that Google puts their profits ahead of the "right" thing to do by supporting companies that we feel aren't being fair with us.
There's also the side of things where bloggers talk about all types of things and get some benefit for their employers because more people read the blog. I guess that's what I kind of do here. I call this an editorial, and it is, but it's also a blog in some ways. It also keeps me busy enough that I tend to neglect my SQLServerCentral.com blog.
There are many thoughts on successful blogs and how to build one for your company. I think that can be good for the company, but what about you personally? What happens if you leave the company? Is your blog lost forever? Most likely it will be, slowly dropping out of the massive cache that Google maintains.
My advice has always been for friends that they should have a professional blog, but keep it professional. No stories about your cats, dates, etc. I know I blur the line here, but I think this forum is a bit of an exception.
My new advice is as follows: keep 3 blogs if you have a corporate blog.
Sounds like a lot of work, but really it's two blogs giving you some disaster recovery. First keep a personal blog if you want. Actually just set one up and put stuff in there that's not related to your career. Put the stuff in there that you wouldn't want someone to ask you on your next interview.
I think it makes some sense to have a corporate blog if you're asked. Use it to put out interesting technical things related to your job or company. But don't expect this blog will get you your next job. It probably works for Raymond Chen and Linus Torvalds, but for most of us this won't help. And you don't want to lose your great technical posts, so set up a third, professional blog for your career. Copy over those posts you want as a part of your online career CV and reference them when you are looking for a new job. Give out this blog to recruiters, interviewers, etc.
You should easily know where a new post should go and try not to mix your professional and personal documentation. Write a new SQL CE app? It could go on all three blogs, but your dog munching on your shoes definitely should only be in one place: the personal blog.