FWIW, I can recommend The Non-Designer's Design Book, by Robin Williams.

It’s short and to the point with practical lessons about things like layout, contrast, etc.

https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133...

I would suggest The Non-Designer’s Design Book by Robin Williams. I have the third edition, it’s great.

https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133...

Would recommend "Non Designers Design Book" for engineers interested in a survey of design.

Proximity, alignment, repitition, and contrast are four basic principles that get you pretty far.

https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133...

The first step should be this book because it so very clearly explains and show-cases the 4 fundamental principles of basic design in a way that is very easy for others to understand: proximity, alignment, repetition, contrast.

"The Non-Designer's Design Book" by Robin Williams.

https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133...

The Non-Designer's Design Book is also recommended: https://www.amazon.com/Non-Designers-Design-Book-4th/dp/0133...

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-Wil...

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.

I'm enjoying The Non-Designer's Design Book - (http://www.amazon.com/The-Non-Designers-Design-Book-Edition/...), as a guy who spends hours trying to figure out why my layouts look like crap, this book has really helped me get to grips with the basics. Which is tbh, where you need to start. After that, just keep reading, designing and failing. Dealing with the inevitable frustration is key (see educational mithridatism). Learning how to use a good design tool also helps a lot. I'm playing with Sketch which is pretty awesome.

I guess in the end, there is no real linear path to learning design. You just sort of have to bumble along until you find your stride.