So I've been reading *[Introducing Microsoft
WinFX](http://msdn.microsoft.com/longhorn/understanding/books/rector/default.aspx)* in physical form. Based
on two quotes alone, I am of the firm belief that Brent Rector rocks.
Quote 1:
I Like XAML, and I prefer to use it to define my UIs rather than using the procedural-type
coding I've shown you so far in this chapter. However, don't think that you'll be able to do everything
you'll need to by using nothing but XAML
I'm finally glad to see someone stand up and give a differing opinion ... many times, the many cheerleaders of coming Microsoft technologies tend to present whatever product they are pushing at the moment in the light that it can, and should do everything. This guy finally stands up and says, look, XAML rocks, but it may not always be the right tool for the job.
Quote 2:
In this book, I don't discuss using Visual Studio because its wizards, fancy code generation
features, and project build capabilities obscure what actually happens under the covers. I believe that
you should understand what a tool does for you before you rely on the tool.
Anyone who knows me knows that I am a big fan of the above methodology. I learned HTML, Javascript, ASP, ASP.NET, VB.NET, and C# all using notepad before I ever touched a more full featured IDE (Dreamweaver, Visual Studio, etc.). I'm not trying to sound all cocky or anything, but I've come to believe, much like mr. Rector has so eloquently described, that the tool should only augment your skillset, not provide it.