Top critical review
3 people found this helpful
Hard to follow along.
on March 5, 2011
Dan knows his stuff. His writing is informative, the FINISHED site template is clean and well-thought out and there are numerous examples of best practices and favorite sites on the web to illustrate his points. Well what could possibly be my problem? The code! The examples in the book are poorly structured to follow along. He jumps from one topic to the next. Would it really have been too difficult to break the code into chapters, maybe providing a start.html file as a launching point for each example? Even a helpful caption or two to go with the illustrations would have been helpful. Perhaps a line number referring to the code? Nope, all you get is the finished home page for the example site. It's up to the reader to figure out what goes where. New chapter, new example, same code.
The book provides just a rudimentary fragment of html as context for each example, this code written on the page looks nothing like the printed sample, it only looks like the finished part of the site. Good for the author, it was easy for him, but now how do I get there? A clue please? Maybe just a hint? How do I make my code look and act as shiny as yours?
I guess (it's never explained) that we're supposed to comment out the finished css and attempt to work along. I started to do this, but as a beginner I messed up a few times not knowing what code referred to what and I finally got exasperated with css that had nothing to do with the chapter that I was working on. I tried. I tried again. I failed. There's got to be a better way to learn than going round and round in tortured circles like this.
I really want to like this book, there's so much content and insight but the code structure makes it infuriatingly tedious.