This reminds me of a script I wrote at work. A lot of us do our compiling in VMs. This means we're left out of all of the fun of hearing fans spin up for large jobs. My script fixes that by polling top over SSH every few seconds and modulating the volume of a looping fan sound by the load average.

I think you could make a pretty good product by doing something similar (varying beep, boops and clicks) for database accesses, server reboots, etc. and making an acoustic uptime monitor. Keep it in a pinned tab and you'll notice right away when your web server's RPS goes way down or way up.

I used the same idea when setting up long-range WiFi (couple of KMs) via antenna for a mesh network.

In order to get the best latency/bandwidth, you need to point the antennas with precision at each other, and in order to know if you're pointing it right, you need to run some tool on a display at the same time, like `ping`, and see when it gets lower when you're pointing it right.

So rather than having to look with one eye towards the horizon, and one eye on a screen to see a tiny number (which I found impossible), I made a quick script that outputs a beep each time ping returns output, with the frequency being higher when the latency got lower. So now I could focus solely on the horizon while using my ears to hear if I was getting in the right direction.

Lots of fun, super useful and makes me wonder (just like you) what other tooling we could use more senses with, rather than just our eyes.

Similar vain: the vim foot pedal: https://github.com/alevchuk/vim-clutch