To my understanding, the point is that it will make you more aware of your limitations, which (again, in my opinion) will make you a better programmer. And I don't think your comparison to physics is apt: your customer doesn't see or care about physics (unless you're designing hardware, in which case you already know physics), and you don't work with physicists. Your costumer _does_ see the visual design and UX of whatever you're building (everything has at least UX) and you (potentially) work with visual designers.
Re:Should a Programmer Learn to Design?
by JoeAltmaier on Tuesday December 13, 2016 @10:35AM
(#13167516)
My sister the Nurse thinks we should all learn basic biology, because, well, she's a nurse.
Re:Should a Programmer Learn to Design?
by namaemuta on Tuesday December 13, 2016 @10:50AM
(#13167644)
I learned basic biology and physics when I was a student, didn't you?
Re:Should a Programmer Learn to Design?
by JoeAltmaier on Tuesday December 13, 2016 @03:19PM
(#13170551)
Had to choose: biology or electronics. Guess which I learned.
Those same arguments could be used to persuade anyone to learn anything.
For my undergrad degree in engineering (and, to a lesser extent, in grad school) we had to learn to work the user experience process -- interviewing users, figuring out what drives them, how they interact with products, what their needs are, how to run product tests with users, etc. Why? Because we might actually have to do it some day. Not so much with visual design. Visual design courses were offered, but not compulsory.
While learning visual design (or UX, or product design, or whatever) might make you more useful in the workplace, and able to wear more hats, I'm still not convinced it will make you a better _programmer_.