We are all very into Extreme Feedback Devices (XFD), so we decided to use all our senses to gather feedback from our projects. This becomes a real challenge once you think about it, because we are naturally very focused on (and limited to) visual feedback.
So we decided to put audible feedback to work.
All our projects get continuously built by two servers in parallel. The first server checks for compilation and test errors, just like a good CI server should. The second server applies every quality metric we found helpful to the code and spits out huge amounts of numbers for every single build.
We identified the numbers that really matter to us and established a simple mechanism to scrape them from the result web pages. Then we associated a sound sample with all possible changes and plugged some speakers to our feedback server.
So now, expect our projects to clearly articulate their news.
To give you an idea of how it sounds, here’s a short list of possible audio samples:
- Fixed an important bug: “Impressive”
- Reduced code crap: “Excellent”
- Introduced a bug: “Humiliation”
Imagine the words spoken like in an old Quake game. Now you can have an eventful build and be yelled at like “Impressive Excellent Humiliation”.
We reserved the biggest coding failure we can imagine happening here to a special audio sample. If somebody introduces new code crap (as determined by Crap4J), he gets ordered to “CUT THE CRAP!” at incredible volume. We used the voice of the inventor of XFDs, Alberto Savoia, taken from his delightful training video for management by numbers (position 2:03ff). The audio quality isn’t convincing, his command surely is.
If you wonder what it’s like to be suddenly interrupted by different voices rebuking or praising you – it’s healthy. You get used to it very quickly, yet the information always catches on. And the information is always relevant.
We call it our “audible remorse”.
Read more about our Extreme Feedback Devices:
- The Code Flow-O-Meter: http://schneide.wordpress.com/2008/10/06/extreme-feedback-device-xfd-the-code-flow-o-meter/
- The ONOZ! Lamp: http://schneide.wordpress.com/2008/10/27/extreme-feedback-device-xfd-the-onoz-lamp/
- The LED Bar: http://schneide.wordpress.com/2008/11/17/spelling-the-feedback-the-led-bar/
September 4, 2008 at 11:35 pm |
Hi guys, I am flattered that you like my extreme ideas for software management
.
I had thought about audio feedback but never got to it, it would make for a good YouTube video if you guys can get around to it.
Keep up the good work and keep cutting the crap!
Ciao,
Alberto
March 1, 2009 at 2:29 pm |
[...] (englisch): http://schneide.wordpress.com/2008/09/04/give-your-project-a-voice/ Possibly related posts: (automatically generated)The Spirit (2008, Frank Miller)oAW Workshop Teil [...]
March 1, 2009 at 2:33 pm |
[...] Comments Extreme Feedback Dev… on Give your project a voiceExtreme Feedback Dev… on Spelling the feedback: The LED…Extreme Feedback Dev… [...]
March 1, 2009 at 2:38 pm |
[...] Comments Extreme Feedback Dev… on Give your project a voiceExtreme Feedback Dev… on Spelling the feedback: The LED…Extreme Feedback Dev… [...]
March 1, 2009 at 2:39 pm |
[...] LED bar sells details to us. The most important issues are already handled by the ONOZ Lamp and the Audio feedback, as both are very intrusive. The LED bar is responsible to spell the news, rather than to tell [...]
March 1, 2009 at 2:41 pm |
[...] Feedback: http://schneide.wordpress.com/2008/09/04/give-your-project-a-voice/ Possibly related posts: (automatically generated)Build Software at Every [...]
September 8, 2009 at 10:22 am |
[...] the last years, we gathered XFDs for almost every human sense. We have visual effects, audible feedback using speech synthesis and even bought an USB rocket launcher for forced feedback needs. With the [...]