Most Helpful Customer Reviews
|
|
329 of 413 people found the following review helpful:
1.0 out of 5 stars
Commits the very sins it condemns, October 10, 2005
I came upon this book via glowing reviews on amazon, citations on websites, and exalted praise from cutting-edge web developers. This was THE book to read if you want to build websites that didn't rely on spaghetti code and deeply nested tables, I was told.
I was greatly disappointed. While I appreciate the overall message of this book and some of the techniques are helpful, not only is it exasperating in its lack of information, but it actually commits the very sins that it relentlessly cites as the scourge of 99.9% of websites - redundancy, verbosity, and lack of clean, clear structure of what little information it imparts.
-REDUNDANCY AND VERBOSITY GALORE
The book really doesn't even get started until Chapter 6 on page 153 (and even that is being generous), after mind-numbing repetition in the form of exposition, bulleted lists, and executive summaries about why one should design and build websites using web standards. There's even a sentence on page 137 that proclaims, "Now let's stop exulting and get down to work." Well, guess what? It's just a tease - and there will be plenty more -- because the proselytizing never really stops.
When the author finally comes around to showing examples and their accompanying markup, it is sadly deficient. CSS that works with the markup is not even shown alongside it, although we are promised to be shown in another chapter. I learned very little about how to actually employ the techniques that Zeldman advocates so strenuously.
The meaningless subheads drove me nuts! Here's a taste: "CSS: The First Bag is Free; The F Word; How Suite it is; Not a Panacea, But Plays One on TV; Inherit the Wind; Miss Behavior to You." I know this might seem like a petty criticism, and maybe people are used to this style from the Dummies books, but 1. They're stupid 2. They impart absolutely no meaning, so if the book is used for a reference, they are less than helpful and 3. The subsections are constantly referred to in all of their absurd and useless glory. This constant reference to other sections by Chapter Number, Chapter Name, Subsection Name smacked of gratuitous page lengthening to me. (If you must refer, why not just use page numbers? Takes up about 1/10th of the space (LIKE GOOD WEB CODE), or better yet, use footnotes!)
-CRINGE-MAKING BANTER
Maybe I'm in the minority here, but I don't get this stuff. I bought a serious, technical book about the new age of coding websites. It cost $35 and at 415 pages, that's about 8.4 cents per page. I don't need breaks for mindless digressions about blueberry tofu pie, what title you were thinking of for chapter 6, or for that matter why you want to write in the first person plural. At times, Mr. Zeldman seems to almost flaunt it in our face that he's wasting our time, e.g., on pg. 214 (after a discussion of how this isn't a CSS manual, and how he's introducing us to the "thighs" and "drumsticks" of CSS), he writes: "On the other hand, how many full-blown CSS reference manuals use the word "thighs" three times in one paragraph? You're right none of them do. Your money was well spent on this book."
And when he does actually explain something, it's like being hit over the head with a jackhammer. It took more than half of page 159 to explain this XHTML rule: "write all tags in lowercase".
-BAD TEACHING
The book is also sprinkled with pointless putdowns like "none of this is rocket science" (pg. 164), but the most egregious teaching technique occurs on page 196, when, mind you, very little actual teaching has even taken place. The author gives an example of markup from the Microsoft homepage (eek!) of what he calls "toilet debris" code and then goes on to say:
"Because redundancy is as bad in books as it is in code, we'll avoid explaining what's wrong with this markup. If you don't know by now, one of us hasn't done our job."
Should the phrase "we'll avoid explaining" ever be part an educational text? With all due respect Mr.Zeldman, I think it's you who didn't do your job.
|
|
|
279 of 351 people found the following review helpful:
5.0 out of 5 stars
<h2 class="review">Designing With Web Standards</h2>, June 10, 2003
<style type="faux/css">
review {
information: priceless
format: real-world, example-based;
clarity: crystal;
history: eye-opening;
audience: essential reading for ALL web profesionals;
humor: witty and wise as always;
timing: perfect - now is the time for standards and accessibility - zeldman explains why and how;
why: save money, time and do the right thing;
how: tons of techniques and proven tactics with real world examples;
bottom-line: actively using dwws as a tool to move my agency and my clients towards standard compliant practices;
}
</style>
|
|
|
12 of 12 people found the following review helpful:
3.0 out of 5 stars
Primarily a book of advocacy, May 11, 2006
While the book purports to give the reader information on implementing web standards, there actually isn't a lot of meaty code examples. The examples are too shallow with insufficent discussion. Mr. Zeldman, however, is very good at advocating why designers and businesses should support web standards. There is quite a bit of advocacy in this book. If you take out the code examples, it becomes a very good "high-level" web standards advocacy book for neophyte web designers, technical managers, and business clients to read. As the book is currently packaged, though, I feel the book does not do what it advertised.
If you're looking for meaty discussion of techniques for coding web standardized markup, you will definitely want "Web Standards Solutions: The Markup and Style Handbook" or "Bulletproof Web Design" by Dan Cederholm.
|
|
|
Most Recent Customer Reviews
|
by Dan Cederholm
by Dan Cederholm
by John Allsopp
by Dan Cederholm
See all 11 books citing this book
