I’m a developer. I program. I make the html that makes the pretty pages. I figured that this book would help me come up with some designs (for those oftentimes rare moments that I’m given a design project). I’d impress the boss and get more design projects. It didn’t quite work out that way.

This book made me feel like I was in design class. A basic page and its “template” was defined, and then there were more examples that if you squint and shook your head, then you could see it fits that template. I don’t think it’s so black and white. If so, then they aren’t that fresh, are they?

If someone is stuck for design ideas, I’m not sure this book would necessarily help since it’s giving more templates. We’re trying to move away from looking like everyone else, right? But some ideas for colors did come from this book, so that’s good.

I enjoyed the idea of boiling down a lot of web designs into a few basic themes, templates, etc. but think that doing so might make it that much harder to break out of the box and be fresh. Or, if you’re like me, once you know the rules, you can break them more easily.

I also liked the little bit of a history lesson that came with this design class. It’s quite amazing what some people did with their websites back in the day, and quite amazing how not so far they have come.

Perhaps this book would be better for the true designer and not so much for the developer wanting to be a designer.

[edit 11/16/2004] Ok, this is interesting. After a few design classes, I like the book more. Still wish it broke it down stupid-style more like Before and After.

Jakob Nielsen is well known for his reports on usability and I really enjoyed his book “Homepage Usability.” I figured that this would be a more in-depth exploration of how to design with the user in mind. Most of the points were on the ball, and very common sense, but nice to see it in writing from someone else. The examples in “Designing Web Usability,” though ancient, fit well with the points.

I kept getting lost, in a way, because I kept getting distracted by the prehistoric examples and data. For example, what do I design for? 640? 770? What is in use today? 1997 was a long time ago in web years. I suppose it’s difficult to have a book with such current data in it, but I’m thinking it’s definitely time for a new version of this book.

There is also a tendency for redundancy. I suppose this is inevitable since whether you’re a search results page or an intranet site, you’re still dealing with the same topics of design.

I do like that even though this book is ancient, it touches on accessibility issues. So many places are only now thinking of that. I also like that testing is mentioned, though again, it is peppered with out-of-date technology which makes all the information seem invalid.

I think this book would be much stronger with new examples, updates here and there to technology and re-released. I think that that was one of the strengths of his other book, “Homepage Usability,” was the freshness of the examples and problems designers are facing. If, and when, there is a new and more concise version of this book, I will buy it.