Listening to this previously missed gem, I hear why it was a Grammy winner in 1992/3. I am happy I had the opportunity to purchased

This book is a self-indulgent rant, that is also poorly edited and structured. If the authors had read their own book and applied their principles to its pages, reading it would have been as much of a pleasure as using software that follows their advice.Why do I give it 5 stars?Because beneath the diatribes and soapbox oration there is a depth of experience and of thought I have not found elsewhere.The authors have considered the issue of what makes using software a pleasurable experience for the user in a depth and with a degree of insight that opened my eyes.

Usability Engineering (UE) is my profession, therefore I was interested in this book. After reading about half of it, I can only say it is a waste of time and money. The author just seems to be in love with his own ideas (which are by no means new- most of his stuff is old wine in a new barrel) but doesn't realy touch the essentials of UE. It is too simple to blame everything on the developpers.For those really interested in UE stay away from this book.

The tone of the book is very negative, I was often distracted by the authors' strange wording choices, confused by the way their "rules" would flip flop, and insulted by their insinuations that *I* am the problem. This book took a tremendous amount of effort to read and definitely was not worth it.

This book is a waste of money and should be avoided. The authors fail to give example solutions or suggestions for many of the problems they fault with today's software. Not only that, they continually slam developers for what they consider to be poorly designed software when its obvious they give little consideration to the real world constraints that exist when developing software. Save your money and try another book, I got very little out of this one.

It seems that most reviews on this book are from software developers, which is why they are so negative. I manage a web development company that concentrates on easy to use websites. From my perspective the ideas and methods are by far the best out there.His main point is that software developers should not create the interfaces we use. This is an important statement that many people need to understand. The software engineer can't design an interface when he/she has no interaction with the users. Even further, it takes a different mindset to create an interface than it does to code.You can't blame the author for setting things straight. What you can do is maybe blame the books stores for putting it in the wrong section. It looks as though too many developers are reading this book for insight.