News for hackers. Stuff that matters.
Re:Should a Programmer Learn to Design? by robert_tweed on Tuesday December 13, 2016 @10:53AM (#13167668)
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.

Re:Should a Programmer Learn to Design? by brightball on Tuesday December 13, 2016 @11:30AM (#13168042)
I'd tend to agree with this assessment. I've never been a designer, from scratch...but once I have a design to work within I don't have any issues with making UI/UX decisions that keep things smooth for people.

This is probably one of the reasons that Twitter Bootstrap has done so well for people like me.

You ask me to worry about visual recognition, spacing, minimizing number of steps, 80% interfaces, etc and I'll have no issues.

You ask me to come up with a color scheme, tones, gradients, proper fonts, line spacing, negative space, etc and I'll curl up in the fetal position.