Watching log files scroll by I have noticed that once you have stared at them for too long you start recognizing the patterns. There's not enough time you read everything that scrolls by you quite often you just know that now something is out of place.
Maybe these soundscapes could provide something similar in a non obtrusive way. Just by listening your brain would be wired to expect certain sounds as consequence for certain actions. If something goes wrong, you would just know it.
I think one challenges is how to take something like this into use. Setting up the the triggers and configuring the sounds feels like too much trouble ("What is the correct sound for this event"). Might be just better to take some ready provided set and learn the sounds.
Right, this is exactly the kind of thing we're thinking about now. We already have integration with a bunch of services (GitHub, BitBucket, etc. etc.). At the moment, you still have to pick sounds for these on signup, but very soon we'll have flexible, sane defaults. Once this happens we will have onboarding in a few minutes for all of our pre-rolled integrations.
Watching log files scroll by I have noticed that once you have stared at them for too long you start recognizing the patterns. There's not enough time you read everything that scrolls by you quite often you just know that now something is out of place.
Maybe these soundscapes could provide something similar in a non obtrusive way. Just by listening your brain would be wired to expect certain sounds as consequence for certain actions. If something goes wrong, you would just know it.
I think one challenges is how to take something like this into use. Setting up the the triggers and configuring the sounds feels like too much trouble ("What is the correct sound for this event"). Might be just better to take some ready provided set and learn the sounds.