The Design of Everyday Things: Revised and Expanded Edition
by Don Norman
4 recommendations


Get it

Recommendations on The Design of Everyday Things: Revised and Expanded Edition

Recommendations from domain experts (curated by Highlyreco)

Vinod Khosla's Review:

Design is not just about how a product looks but also how it works. In this book, Jesse deftly describes the various facets of user experience and how they are all connected from how the product looks and how it works to the overall company strategy and how every CEO is a designer whether they recognize it or not. — Irene Au

Ref: http://www.khoslaventures.com/resources/reading-list

Joel Spolsky's Review:

Donald Norman's classic The Design of Everyday Things (also published under the name "The Psychology of Everyday Things") is one of the best books on "UI design", even though it talks more about doors and and refrigerators than computers. This was a groundbreaking work for its theory of affordances which I talk about it chapter 4 of my UI book, which remains one of the most influential ideas in good design of everyday objects.

Ref: http://www.joelonsoftware.com/navlinks/fog0000000262.html

Jeff Atwood's Review:

It can be incredibly frustrating to develop software, because so much can go wrong. A lot of what we do is defensive: trying to anticipate what will go wrong before it does. It's mentally fatiguing, and can eventually manifest itself in some negative ways. I sometimes describe this to non-technical people as building a watch with a thousand moving parts, all of which can fail randomly at the slightest provocation. Good times!

Designing software is difficult, to be sure, but designing a door is difficult too. The nuances of design extend into every object you touch, whether it's some hot new SQL engine, or a humble shoe. This book will give you a new appreciation of the "devil in the details." If designing a door isn't the no-brainer we thought it was, maybe it's time to give ourselves a break for not being able to design software perfectly, either.

Ref: https://blog.codinghorror.com/recommended-reading-for-developers/