Here. Want to write for MSDN online? Here's how.

Here. I don't know why an ASP site is reviewing a WinForms book, but they do a thorough job and, of course, I like their conclusion: "If you are looking for a Windows Forms book, don’t let this one slip out of your hands. The book has such insight and experience included that every reader, beginner and professional, will get benefit from reading it."

Here. Rory built me an RSS feed to track book reviews on Amazon.com. And then he thanked me for letting him do it. You're welcome, Rory... BTW, to complete your Vain Author's Toolkit, you'll need junglescan.com to track a portfolio of books' sales rank. If those ain't web services, I don't know what are!

Here. The one where I list the steps I use to figure out stuff that isn't documented.

Wednesday, October 15, 2003

I got an email today from John Reilly today asking me a question I get from time to time:

I got my signed copy of your book. It is a great read. You have information that a friend and I have been trying to dig out for weeks.

Which leads me to our question. How do you find out all those details? They are not to be found in the MSDN documentation, as far as we can tell. Do you just experiment, like we do? We have been unable to find any .NET training that is much more than how to use the IDE. Alan and I crave detail, meat, the stuff of your book. Seriously, how does one obtain this seemingly inside information? We are personally and professionally motivated weenies.

Now that I’m a Microsoft employee, I have access to not only the source for most of what I’m researching, but the architects and internal mailing lists populated by the developers on the project, so that really is “inside information.” However, over the 8+ years that I was a contributing member of the Windows developer community, 99% of what I’ve done has not been based on inside information. So, before I had access to internal info, how did I figure stuff out if the docs don’t answer my questions? I do the following, in order of decreasing frequency:

• I experiment, writing hundreds of projects consisting of 10 lines of code or less to experiment with particular features
• I read the source, even if that means reverse engineering it first (Reflector is fabulous for .NET code)
• I search on the Microsoft-specific Google search page
• I IM, email and call my friends who know more than I do (which is most of them : )
• I ask questions on my favorite mailing lists and newsgroups
• As a last resort, I ask my friends at MS. Buying a Microsoftie a beer at a conference, being smart in online forums and saying nice things about their technologies are all excellent ways to gain friends at MS

Here. I think those Amazon guys knew I was talking about them...

Here. The one where I describe RSS to the world's youngest mutual fund manager and my Mom.

Here. I've noticed that lots of folks have nice things to say about "Windows Forms Programming in C#". I thank you and my publisher thanks you. If you do post a review, you'll likely get an email from me asking you to post it on Amazon.com. That's because Amazon has noticed that it's the number of reviews of a product that determines whether something sells better than it's competitors, not the rating of the reviews (although feel free to say nice things... : ). I'm posting this here to a) warn you that a review on my book is likely to get you an email from me and b) because Scott Galloway's Contact form is busted ("You must enter a search term"), so I needed *some* way to ask him to post his review on Amazon. Thanks!