One Year Blog Anniversary


Ok, I am a real sucker for all things sentimental, such as Anniversaries.


One year ago, I made my first blog post, a huge script code snippet that illustrates some frequently misunderstood concepts. Never mind the fact that it was not until four months later that I made the next blog post and a couple months after that when I figured out that it is better to make regular daily posts instead of bi-weekly Q/A marathons… but here we are, a year after it all began, and I still find and get interesting things to write about…


Of course, I have to take a moment to evaluate exactly what I have achieved and re-evaluate exactly what I want to accomplish…


Ok, so it is time to play with numbers. I decided to take a stroll through all of my blog posts and do a rough “popularity” score of each blog post to see what people like to read. Based on that statistic, some of my most popular blog entries include:



Incidentally, the 401 diagnosis article is also my first 10K blog entry. People really seem to like searching for and then reading it. The other articles are also what I deem to be basic “HOWTO” articles on IIS functionality… and are at the root of most of the frequently asked questions, so having a blog entry to reference has made answering newsgroup questions that much easier. It is kind of cool to just reference blog URLs instead of KB articles. 🙂


Believe it or not, it is far easier for me to publish the correct technical information in a blog entry than for me to get that information into a KB article or documentation. The documentation process at Microsoft just plain sucks at all levels:



  • I never get the correct technical information published because some technical editor with zero clue on the subject decides to change my words without telling me. I hate talking through a middleman.
  • There is a mountain of red-tape just to get a change made. For example, it takes me at least six months to make a fix to MSDN documentation, from when I first notice something is wrong until the fix is published. That is frickin ridiculous in the Internet age.
  • I think documentation is very much a “product”, just like software products… but amazingly, it is NOT treated as such within Microsoft and is NOT produced with the same level of quality nor project management as its software counterpart. Frightening. Makes me want to shake it up.

Anyways, I can rail against that all day long and plan to within a future blog entry. This is just a sampling. 😉


I guess I should take a quick poll and see what you would like to see me do more/less within this blog… here is your chance to make comments and suggestions. 🙂 Because otherwise, I will just continue writing about whatever I feel like talking about, in accordance to my blog’s tagline…


Virtually Yours,


//David

Comments (2)

  1. Congrats on a year of blogging. Your posts have really become a great resource. Yesterday’s post, for instance, on anon auth POST failures, while not new to me (and probably others who’ve worked with IIS and read the KB), provided not only a clear explanation, but also added that extra little nugget of interesting knowledge by explaining POST success for integrated auth. It’s like KB++. 😉

    Looking forward to your next year!

  2. David Wang says:

    Eric – Thanks for the encouragements. I appreciate it.

    I guess a part of my "style" is that I like to understand things things from top to bottom, inside out, so that I can use that information to resolve issues through critical thinking and not pattern matching.

    Unfortunately, KB and most documentation assumes the user search and pattern match their way to a possible solution because they have some pressing problem… so they do not really focus on clear explanations of "why" and "how" — just match your problem with the recommend solution and there you go.

    Of course, this leads to a deluge of KB articles that are near duplicates of each other *because* of user pattern-match, which often make it more confusing and frustrating for users trying to learn and figure out what is going on.

    So, here is my little coup against the established MS documentation community and attempt to build up a base of IIS knowledge. 🙂

    I intend to keep writing up what I think KB articles should be, in my own way… without technical editors diluting/distorting the facts, the red tape of making changes to MSDN, directly from the right sources, and directly cover the customer issues that I have observed from years of monitoring/answering newsgroup posts.

    //David