I totally agree that there is an often loud minority calling for this sort of thing: "I am an expert. I don't need styling or white space. I want every last s

I totally agree that there is an often loud minority calling for this sort of thing: "I am an expert. I don't need styling or white space. I want every last square centimeter of space filled with 8pt font. I demand information density!" (aside: these are also the same people who say that JS-based UIs are slow and server-side HTML is faster, despite the fact that backend latency is 99.999% of the problem but that is another discussion...) And yet, in my lived-experience at an unnamed Big Co when we did lots of UXR work in the on-call, monitoring, and incident management software/tooling, when it came to people being the primary on-caller handling a page for an incident when the company is losing millions for every minute of downtime that the 8pt font information dense UI they said they wanted actually led to increased stress, more mistakes, longer time-to-mitigation etc. Turns out that a carefully and deliberately designed UX and information architecture and - gasp - white space (that was all carefully and minutely tuned to specific CUJs over many rounds of research and prototyping) is really important. Even if you have all the information available, just throwing stuff at the screen doesn't always help IME. Less is often more.