Some of you are probably wondering why I sometimes blog on such strange topics. Great question! There are lots of reasons:
 1.) My area of expertise (ie, the only thing I know more than you about) is the CLR Debugging Services. Based off blog comments and email I get, I judge there to be about 20 people in the world (literally) who actually care about that topic. That means the rest of you are going to be at least mildly bored anytime I blog about the stuff I know the most about - which is what I'm statistically most likely to blog about. Anytime I steer away from my area of expertise, there are hordes of readers who know it better than I and they quickly point out the mistakes I inevitably make. (Like this fiasco where my post was so wrong I actually had to take it down lest somebody accidentally stumble upon it and be mislead).
 2.) Sometimes it's not clear what's boring. It's actually funny in retrospect: Some posts that I thought people would love, they hated (as judged by very low hit counters). And some posts that I thought would be lame got lots of hits. 
 3.) Some entries are to answer a specific email I get. If I blog the response, I only need to answer it once.
 4.) Some entries are "prerequisite" entries. For example, I'd actually like to blog about topic A, but I need to blog about topic B first so that A makes sense. And putting A and B into the same entry is too long. For example, I did this (idea for search tool), this (how to programmatically search), and this  (use clipboard as input) so that I would have the perquisites for this (final sample code for tool). Same with this (deriving from TextReader), this (comment on polymorphism from previous post), this (nesting C#'s yield statement), and this (building a TextReader around yield), so that I could do this (building a XmlReader around TextReader), which in turn was a prerequisite for this (spewing Xml from a pdb).  Sometimes the intermediate entries may be boring.
 5.) Some entries are for my own selfish benefit. I may be learning a new technology (such as Cascading Style Sheets) and want to write about what I've learned.