"Thinkers are rare; doers are rarer; and thinker-doers are rarest."

This is a book that presents the advantages of doing a design with div + CSS instead of tables. The books starts with a reasonably complex design and show its implementation using CSS. If would have been nice to also show a "table" implementation for comparation.
From my point of view the book fails to "convert" me to CSS. I DO understand all the theoretical advantages of a CSS based layout but the reality is quite different. It takes a LOT of time to create a reasonably complex CSS based layour that works fine on multiple browsers (it takes even more time if you want to support older versions of Internat Explorer). Honestly i do prefer to use a table based layout and use the extra time to make sure that i have a solid application.
But that's just my point of view....

The latest HTML5 draft has support for SQL (yes....Structured Query Language)execution. While the browser might become a "application platform", sql execution support in DOM is soooo NOT the way to go.

Finally...i'm the happy owner of a XBOX 360 ( i went for the Premium version with the PGR 4 bundle....and i was lucky to get a new and quiet Benq drive). So far it's funtastic. I'm playing on a 40 inch Samsung LCD TV(1080i....hope to get a HDMI cable and hook it on 1080p) and the experience blows out of the water the PC gaming experience.

More impressions after i'll finish PGR4... :D

I'm working with a customer which insists on using his "shared" dialogs. Basically they've put together a library which contains windows forms (with included functionality) and a overblown API above which controls the functionality.
The really sad part is that i have to "configure" the UI with something like this :
BadDialog dlg = new BadDialog(); dlf.buttonOk.Width = 300; dlf.buttonOk.Height= 400; ....
It's an awful and painful way to "reuse" code (it seems that for every line of code they've put in that library i have to write 3 lines to use it).
Sometime code reuse it's the only viable solution.