Do you really want long running examples in tech books?
Most of them were well structured, well designed, and guaranteed that nobody would ever learn a darned thing from them - but that wasn't the point - the point was that the company laying out the unbelievable cash for us to create this garbage was getting an even more unbelievable break from their insurance company if they could prove their managers were "trained." In other words, there was this whole chain of lies that led to me getting paid to produce utterly worthless crap. All of which would have been fine, except that I wanted my life to have some meaning, so I moved to Prague and went to work on NetBeans :-) I'm just wondering if the book-wide example, where you start in chapter one writing the login page and end up with your very own amazon.com at the end actually teaches you how to write anything but amazon.com. It's always seemed like a cop-out to me - I want to know the why's, so when I have I problem I can intuit the solution - and that's how I've always tried to write. It seems like the tech industry rewards rote instructions more, and that's a pity.