Looking at a bunch of developers assume expertise in interface design while shitting all over design as a field used to be a rage bait situation for me, but it’s fruitless. I’ve been both, and I was a developer long before I was a designer. I don’t think you have to be an expert to criticize an interface, and you definitely don’t have to like it, and some number of designers undoubtedly agree. But I encourage you to consider that the osmosis-learned nibbles about design and that Edward Tufte book you enjoyed might not qualify you to judge the competence of the better part of an entire set of professions. Most developers don’t even know what actual problems designers are tasked to solve, let alone evaluate their efficacy. Developers are a lot better at knowing when they know something than realizing when they don’t. NOBODY is good at discussing what they’re used to with what’s objectively good or bad. The “I don’t care what anybody says — this is just objectively bad” attitude is something that arises with literally any interface change in any major product. Developers have a very different usage style than most people and when you get a bunch of people in one place agreeing with each other without any outside voices, that’s an echo chamber at best and a circle jerk at worst. To be clear, I’m not even discussing, let alone defending the design: I’m countering the cocky obnoxious designer hate that pops up in these threads.

PS— Edward Tufte has some interesting perspectives on data visualization but the reason he’s so popular with the engineering crowd is because he was an engineer and he makes cut-and-dried rules about things that are easy to understand without any design education, and explains them in a way that appeals to engineers. Reading that book is better than nothing, but it’s gives laypeople about as much understanding of design as a “[language] cookbook” gives laypeople an understanding of programming.