www.jlion.com

Thursday, February 22, 2007

Recently I've been re-reading to The Fountainhead, by Ayn Rand. Actually, to be completely accurate I'm listening to it in audiobook format during my daily commutes to and from work.

I first read The Fountainhead in high school and remember liking it very much and finding it inspirational. I aspired to be like Howard Roark, to be an artist with integrity.

As I re-read it now, with several decades of experience between me and that first reading, I see things that I didn't see the first time through. Firstly, Ayn Rand is not the most subtle writer. In a way, The Fountainhead is to philosophy what The Goal (Eliyahu M. Goldratt and Jeff Cox) is to factory planning; the characters are drawn in broad coarse strokes and exist primarily to move the book's argument forward.

The book is, of course, at least nominally about architecture and architects and as someone who fancies himself a bit of a software architect, it's interesting to consider what Howard Roark would be like if instead of buildings he designed software. I'm not yet ready to pass a verdict as I'm at about the middle point and Howard Roark could yet turn out to be quite a different person than he now appears.

After a bit of research I did find that I'm not alone, though. Joel On Software mentions Ayn Rand and there are some interesting comments. Here is the link: http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=147596.

I also discovered that there was a movie made of The Fountainhead. IMDB and Netflix commenters generally agree that it is not best of genre. I am planning to see it when I have the chance but after I finish the book. One interesting tidbit I picked up from reading movie reviews was that Ayn Rand had wanted Frank Llyod Wright to design the architectural models featured in the film but had relented when Wright's fees were too high. This led me then to compare the life of Wright to Rand's character Roark. Short answer: Not much alike.

Friday, February 16, 2007

I always use the "Publish Web Site" option to deploy my ASP.NET 2.0 projects. I do this for several reasons: I like knowing that the code in a production environment is the same as the code in my development environment, I know that published (compiled) pages exhibit better performance than uncompiled pages, and I like that the source code of my web applications need not be deployed along with the application itself.

However, "Publish Web Site" deployment has its own bugaboos. There are three files for each published web page that must be kept in sync, and for large web sites there are often hundreds of files in the BIN directory. Updating the code for just a single directory or page can be daunting.

The VB2005 Web Deployment Project addresses this issue. Using this free Microsoft add-in, web applications can be compiled either to a single dll or (as I prefer) to one dll per directory. This makes deployment of site updates much easier.

More information about the VB2005 Web Deployment Project is available on Scott Gunthrie's blog, here:
http://weblogs.asp.net/scottgu/archive/2005/11/06/429723.aspx