Rating: 
Summary: I feel very strongly about this book
Review: This book's glossy pages look and feel good but it's amazing how little information the author succeeds in sprinkling here and there in the actual text.The book is an armchair tour of some sites that in many cases have already been proven failures. We get very little information about how the sites were made and what innovations were involved. You would be much better served by looking at the sites' html source code. It's not a pleasant thing to say about someone else's work but this volume is simply a waste time and money.
Rating:
Summary: Not an architecture book
Review: This is an incredibly disappointing book - all style no substance. I wonder if the author actually understands the basic concepts of web architecture. This book provides a tour of some okay sites, and does point out a couple of nice features, but it doesn't go into any real architectural issues, either from an information or infrastructure standpoint. It's ironic that Mr. Andres recognizes "Content is King" for web sites, but has failed to provide any real content for his book.
Rating:
Summary: Not an architecture book
Review: This is an incredibly disappointing book - all style no substance. I wonder if the author actually understands the basic concepts of web architecture. This book provides a tour of some okay sites, and does point out a couple of nice features, but it doesn't go into any real architectural issues, either from an information or infrastructure standpoint. It's ironic that Mr. Andres recognizes "Content is King" for web sites, but has failed to provide any real content for his book.
Rating:
Summary: First it hurts, then it makes you sick...
Review: This is quite possibly the worst book I've ever read in my life. I didn't realize someone could create something so self-congratulatory that they lost any and all vision of contradiction. There are examples of 'great architecture', complete with content hierarchy diagrams, that were obviously poorly thought out, if thought about at all. Common problems like separating support and marketing information, or placing/labeling company wide information have no formal identification or treatment. Essentially this is a tour of 'sexy' sites made in 1998 - which wasn't really that much of a break through year for usability or architecture. If you want to see what happened when a mass of CDROM designers started making websites - this is the read for you... Personally, I stole this book from the office just to ensure that some producer wouldn't read it and take it seriously... It's that nonsensical.
Rating:
Summary: First it hurts, then it makes you sick...
Review: This is quite possibly the worst book I've ever read in my life. I didn't realize someone could create something so self-congratulatory that they lost any and all vision of contradiction. There are examples of 'great architecture', complete with content hierarchy diagrams, that were obviously poorly thought out, if thought about at all. Common problems like separating support and marketing information, or placing/labeling company wide information have no formal identification or treatment. Essentially this is a tour of 'sexy' sites made in 1998 - which wasn't really that much of a break through year for usability or architecture. If you want to see what happened when a mass of CDROM designers started making websites - this is the read for you... Personally, I stole this book from the office just to ensure that some producer wouldn't read it and take it seriously... It's that nonsensical.
| 
