Found in 8 comments
by skittleson
Working Effectively with legacy code ( and The Design of Everyday Things ( )

Both have a huge impact on how I work with code and design them. Trying to explain these concepts are hard without context. Sometimes i just copy/paste the sections i think they could benefit from.

Original thread
by ankyth27
Here are some: 1) Don't make me think twice: 2) 100 things every designer must know: 3) Design of everyday things:

While UI/UX is more of a field where you get better by practice and observation, yet these books can surely help you build a solid foundation.

Original thread
by taeric
This seems to be blurring a use of "design". Not all design is chrome on top of things. Some literally leads to better use. Some design is required for safe use.

I think it is oversold, but the book "Design of Everyday Things"[1] goes over this for many common items. There is a long section on doors with many interesting points to consider.


Original thread
by onli
If you like that article, you might also like Donald Normans The Design of Everyday Things, It has a lot more examples for these kind of bad designs, and it also explains why these designs are bad and what makes a good design. I can't recommend it enough, everyone that ever might design a product or a GUI should have read it.
Original thread
by ErikAugust
Don Norman would claim it is the designer who is at fault:

Interesting discussion in itself.

Original thread
by nathan-muir
The Design of everyday things [1] (Found on Coding Horror's recommended reading [2]) was crucial in understanding how people intuitively interact with the world around them - including your web application - based on the visual cue's you provide.

While this article provides some metaphorical fish - I found the Design of everyday things helps you become a fisherman.

EDIT: Swapped the order of references.



Original thread
by dmix
Right, many software devs have read The Design of Everyday Things [0] and understand the value of usability. But they didn't read Don Norman's follow up book Emotional Design [1] which explains that usability is only 50% of the answer - emotion is the other 50%. And emotion often means pretty, or at the minimum a positive UX.



Original thread

Looking for a good book? Subscribe to the weekly newsletter.