No. But they should start to appreciate it, and the people who create it, more than they do. All too often, it appears that programmers see design as a lipstic

No. But they should start to appreciate it, and the people who create it, more than they do. All too often, it appears that programmers see design as a lipstick-on-a-pig kind of process, i. e. a replaceable skin that possibly improves the color scheme. My favorite example is the guy who bragged that he saved xxx kb of page weight by replacing the fonts on nodejs.com (or rubygems? one of these repositories) with Arial, because "all sans-serif fonts are the same anyway". I'd also point to the frequent complaints about medium.com. It doesn't even matter if that design is any good – it clearly succeeds at what it's supposed to do. The most obvious path to a better appreciation of the meaning and methods of good design is probably Edward Tufte's books[0], which is one of the "crossover" works that appeal to both designers and the more scientific-minded crowd. [0] https://www.amazon.com/Visual-Display-Quantitative-Information/dp/1930824130/ref=as_li_ss_tl?ie=UTF8&linkCode=ll1&tag=telomere01-20&ie=UTF8 https://www.amazon.com/Visual-Display-Quantitative-Informati...