I've got to get this gem down before I forget.  I'm sitting in Web322, ASP.NET 2.0 Under The Covers - Exploring Page Life Cycle, Internals and Compilation Model.  We're in the introduction and we're getting some of the supposed benefits of dynamic compilation in ASP.NET 2.0 beta 2.  It goes something like this:

Say you get your code moved out to stage, and you need to make a change to a class file.  You can go ahead and do it, and it's such a productivity gain, you don't have to go all the way back to the tool.  ARE YOU KIDDING ME?!?!  That's a productivity gain?  We don't want to go back to the tool to make sure that change is persisted in some sort of version control or change management system?

Why is there such a push to cater to the lowest common denominator?  Why should we be able to drag and drop an enterprise application?  If software development is difficult, it's supposed to be.  Just because you use a tool or your business card says developer/programmer/code wizard doesn't mean you are.

So we get this in the first 45 seconds of the presentation, mmmmm nothing tastes as good as bile.  Even the drag and drop demo is yellow screening, I'm guessing I'm not going to get that deep into page life cycle or control state / view state changes, it's certainly not going to be a 300 level discussion.