During it, he commented "while I was on the plane from San Francisco to Japan I hacked on ...", and then "while I was on the plane here I hacked on ...", and I wondered what is the carbon footprint of miyagawa's modules?
Nicholas asked me this at the pub after LPW 2009, and it indeed was an interesting question!
I guess the fact that lots of my code is written on the plane reflects that many of my software is written (and is improved) using the CDD methodology - Conference Driven Development in the first place.
We submit a talk proposal to a conference, assuming we could make the software actually implemented and usable between now and a time when a conference happens, and it definitely forces us to actually write the software. Speaking about vaporware in a conference is embarrassing!
Also, by speaking about the same software multiple times in multiple conferences, we're forced to update the talk so as not to get bored by ourselves, and that helps us to improve the software, again.
So now let's call it ICDD, Iterative Conference Driven Development.