I'm sorry, but I don't think you could be more wrong in this case. Calling the attention to detail in design "trivial" is not just insulting to the designer an

I'm sorry, but I don't think you could be more wrong in this case. Calling the attention to detail in design "trivial" is not just insulting to the designer and the company, it overlooks a very important fact—Prismatic is about the user's reading experience. Two points: First, just because they are able to explain the design rationale and historical context of their typographic decisions doesn't mean they necessarily agonized over them for months. A good designer knows these things from experience. I'm very happy that they took the time to explain them, and I don't think a blog post can be considered a frivolous use of a company's time. Second, you seem to assume that there isn't anyone else in the company thinking about what you deem the "more important problems," or that they haven't already been through an earlier MVP stage where they focused primarily on technical issues. Developers feel insulted and misunderstood when MBAs dismiss their efforts as fungible or underestimate their value, or the time required. It doesn't help when the equally vital role of designers is relegated to "triviality."