I found that the concepts he covers in that book can even be applied for good software API design.
Also, he did spoil doors for me. Pretty much every building I go into now annoys me because of the stupid door handles they pick.
And then if you're interested you can dig deeper into colors, layouts, types...
A lot of it is common sense, but only in hindsight.
This is true, but it's true for anything. Reading a programming book won't teach you to program unless it presents problems you can build on actively throughout the reading. You need applied reps, otherwise you'll at most get some vague inspiration or enjoy/hate it.
This is why I don't read practical books anymore unless I'm prepared to practice what I'm supposed to be learning about during the course of my reading. This is also true for videos.
More seriously, I have read the design of everyday things about 10 years ago and it was one of the most boring books I have ever had to go through. I only remember doorknobs and something about affordances. Read refactoringUI as well, some vague shiny UI tips of which can't remember any but 'have decent spacing'. I still can't design even a simple form. I am starting to suspect that if one wants to be good at web design one needs to start doing lots of web design until one gets better. Reading books may come later to place that practical knowledge in some coherent mental framework.