I did similar experiments longbtine ago, but wasn't satisfied with results. Still, I believe this idea has great future if done right.<p>One principle I was experimenting with was "related events should create related sounds." A particular case is hierarchical events, like parent-child operations or requests, that should create "hierarchical sounds" that are octaves apart. For example, the parent request produces note A4, so its child request should be A5. Some cleverness needed to express different types of requests with different, but related sounds. Errors should be clearly audible too.<p>Real life applications need to work with huge amounts of data: so you could hear a lot in a few seconds. I recommend you to watch a movie about a airplane company investigating a crash by listening to recorded noises: a professional listener gets to hear a lot of insights, and gets subsequently killed for that (forgot the movie name).<p>Also, think of a huge file with logs: requests, errors, and all sorts of garbage in it. A few millions of records. How do you hear it in 1 minute and get something useful out of it?<p>Another association is dial-up modems from the 90s: those would take minutes to connect to the internet, "logging" their progress to speakers, and with some experience, you could distinguish diffrent stages of connection or errors.