/home/todd

So for the past week I’ve been meaning to write up a description of the general awesomeness that was IUI ’09, but with end-of-term craziness in full force, it’s going to have to wait.  Suffice to say it was a fabulous week full of wonderful people and some fascinating research.  Photos are slowly making their way from my notebook to Flickr, and once the VLHCC ’09 submission deadline passes, the process should speed up.

Speaking of, the past week has flown by as we prepare our paper, and I’m certain the next two will be similar.  Today and tomorrow I’ve eight transcripts to code, plus an abstract to write and a clever title to generate.  Feeling pretty good about it all at this particular moment, though; met up with Andrea at a funky new coffee shop (Vibe) downtown this morning, and ran into her friend Lisa as well.  Now I’m exporting our final transcript video from the lab, then heading home to throw open some windows, put on a kettle, and code until I can code no more (and maybe a bit past that, we’ll see).  The past few evenings have ended with mini-marathons of Series Three Doctor Who, and I’m looking forward to finishing that off late tonight.

Yesterday I was notified that my research group’s submission to IUI’09 was accepted!  This was the first research study and resulting publication that I led, and I’d honestly not been expecting it to be accepted on the first try.  So yay!  That’s two publications in a year and half–not a bad start, I suppose   The paper detailed a formative study of barriers end users encounter when attempting to “fix” [i.e. debug] machine-learned programs, like junk mail filters or hand-writing recognizers.  These sorts of machine-learned programs are becoming increasingly common in software, and since they need to tailor themselves to a particular user’s needs, that end user is the only person available to debug them if they misbehave.  It’s really a whole new research field that can build upon existing data about end-user programmers debugging in more traditional environments, like Microsoft Excel, but the machine-learned component is a significant change from such traditional models of source code.

Now we have three weeks to address the reviewers’ comments and get a camera-ready version to the conference organizers.  The conference itself is in Florida this February, so with a little luck, I might be able to afford to go and present the results in person