This is how my blog looked in 2002-2003 years when I first created using straight HTML. Back then there were a few people blogging and some still are. They’ve become quite knowledgeable of what works and what does not. I didn’t started real blogging until 2006 really, before that I only used my html website to share code. That’s really what I believe that had value back then. Now in 2009 still believe samples and code concepts bring value to developers. The best way to learn fast is explaining the concept and provide a sample code snip of what you just explained.
Since then many developers have claimed their blog in many open Blog places like WordPress or Google Blogger. This is fine, yet I do believe that developers should go a little deeper 
than that and use one of the multiple blogging engines out there. My reasoning is very simple, provides a personal sandbox to add functionality and show your demos right there and then. Extending the blog will create a complete unique website and is not a theme from one of those writing places, so when something cannot be publish because the blog host does not allow javascript, you can go ahead and write your own module.
What I’m trying to say is that developers do not have an excuse for not hosting their own blog, creating their own blog engine, or extending an existing one.
There are wonderful blog engines that you can extend or write custom modules for, my favorites are:
Graffiti
The one I am using right now created by Telligent as a CMS. Very customizable and easy to personalize as well extremely powerful.
Community Server
I used CS 2.0, 2007 and 2008 previously before moving to Graffiti, is a great ASP.NET application with much more than just blogging, creates an complete community.
SubText
Phil Haack application from the old .Text blog engine, very popular in the open source world and or course IS an open source engine.
dasBlog
Another open source blog engine for ASP.NET 2.0 using xml files instead of any database backend, very portable yet an scary thought to have xml files as the posts. A design from Scott Hanselman.
There are more choices than the ones above, I stayed closer to Telligent for my choice for a blog, even they are not open source, they allow developers to extend their applications. I personally going against what I am doing, I would recommend to select an open source blog engine for your needs. Make sure you can use LiveWriter for your posts and posting code will look formatted.
Whatever you are a casual developer with a few pet projects or a professional one, you have a few code snips that you should share with the community, having a blog will allow you to do just that, or to keep code for later use in other projects as the years go by.
Cheers
Al
Follow me in twitter | bookmark me | Subscribe to my feed | Add stats to your blog