IMO, a book every developer should read is "The Non-Designers Design Book" by Robin Williams (no, not that Robin Williams). It's short and to the point, so it

IMO, a book every developer should read is "The Non-Designers Design Book" by Robin Williams (no, not that Robin Williams). It's short and to the point, so it won't take long to read, yet it covers all the basics of design to just the right level for the average developer. "Design for Hackers" by David Kadavy is also quite popular, but IMO it just takes longer to say the same things. Amazon links for the lazy: https://www.amazon.co.uk/Non-Designers-Design-Book-Robin-Williams/dp/0321534042 https://www.amazon.co.uk/Non-Designers-Design-Book-Robin-Wil... https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133966151 https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133... Edit: Since several of the latest comments seem to be saying similar things about programmers not "getting" design, I think one thing that may come as a bit of a revelation is that design starts with a hierarchy of information and there are certain rules for how that information should be presented. There is an artistic aspect to compelling design, but when it comes to things like wireframes and UX modelling, your average programmer probably has more design skills than they realise.