What are you're thoughts on "punishing" and "rewarding" teams for automatic software builds?

I found these two approches interesting :

Who broke the build?

Croissant Build

The first one, I find really fun but I can see where and when it'll go wrong .

The second, I'm a little bit worried for my waist-line .

Here's a nice and easy to use Javascript library for internationalising a web application (handy for Phonegap and co.) :

http://keith-wood.name/localisation.html

I was happy to follow this first great talk by Axel Rauschmayer. It was well explained and corresponded to the tech-level I hoped for (reminding the basics, presenting the good patterns to use, and the trouble-shooting that can be met). The main idea that I noted is that Javascript has a big potential to be seen everywhere (client, server, desktop, mobile, database, ...), have a good understanding of its workings is capital nowadays (both for its potentials and limits).

The opening keynotes were presented by two personnes.

Firstly, Martin Görner (Googler) invited us to get the Chrome for Android (ICS). The Javascript motor was rewritten, is faster, and incorporates gestures (you can, among other things, manage your tabs like a stack of cards!). They optimised Canvas, 3D, CSS, ... On the other hand, WebGL, WabAudioGL API, and Flex don't work yet. But, remotedebugging works !!11!1!

Then, Claire Blondel, who is a quality engineer, took the mike. Her talk puzzled quite a lot of people but echoed so much of my childhood. Through examples of her travels and her family, she explained how, in France, making mistakes is "inexcusable". This, according to her, can bring low self-esteem, lack of autonomy to deal with mistakes, and lack of perseverence to deal with them.

I'll be all day today at the Mix-IT convention following several tech-talks .