Scoble writes about Chris Brumme's weblog, which is hands down the  most technical .NET weblog (or Microsoft weblog, period) that is out there right now. If there is one that is comparable, please enlighten me. I like Brumme's site a lot, I have learned quite a bit from reading his posts. The site is highly detailed, and provides great insight too into some of the design decisions/tradeoffs that were made for the CLR. 

Reading Scoble's post reminded me of something. When I started this blog, I wanted it to be "more technical" than many of the blogs I read from technology people. Many of those folks are quite accomplished, but they don't limit their blogging to technology. Also, the nature of their work doesn't allow them time to actively discuss technology topics in depth on their sites. The reason I wanted to start such a blog is simple: I'm looking for feedback and stimulating discussions about technology issues that interest me. Discussion lists fail the "signal to noise" test, so I thought a blog would be more appropriate. Plus, I'm writing a book on Yukon and thought that a blog would be a great way to get some discussion going.

I've run into a couple of problems though that are specific to my situation. First, Yukon is under NDA still and will be for a number of months. So I can't really talk about much that is in there. Second, even if I could talk about it hardly anyone has access to it or is using it yet.  So the feedback I would get would be fairly limited. I could blog about other things though, and from time to time I've speculated on topics or have provided high level assessments of pending Yukon or Longhorn features. But that kind of writing does very little to stimulate discussion or facilitate learning. I've also managed to step into some religious topics as well (I'll be trying to avoid them in the future).

So, how do you go about writing a good technical weblog? Well, I'm not really sure. My thinking for now is that this is something that you can't really "force". You either have the knack for it and have material that is appropriate to post or you don't. For now, I'm going to continue a more "conventional" style of posting on matters of interest to me. When Yukon starts to gain a little more visibility, I'll try to spend some time on some more technical entries. I may even start another blog to segregate the technical from the non-technical. I'll have to wait and see.