Basically, like the bridge of Enterprise D (or its main engineering).
The reasoning here is to recreate the experience of "feeling" the machine. Like drivers do with their cars. Like we could do in the past with HDD sounds, and now sometimes with fan noise.
Last time I mentioned it publicly, someone told me they use widgets with resource usage graphs for that purpose. I've started using them too, but I noticed that I generally don't look at them. Even semi-transparent, they're mostly just a blob of color that occasionally obstructs some UI I need to interact with. But sound is a separate channel, and easier to process subconsciously.
Anyone knows of tooling relevant to implement this idea?
 - During a recent debugging session, I accidentally gained some insight about the problem by noticing the fan is making less noise than it should during certain tests.
I got early access and wired it into our software, which essentially processed streams of various events. And you could get a sense for when the pace picked up, or something unusual was happening more often than normal. Sadly the project was shut down at some point.