I found this report on the USENIX JVM Symposium, 2002, not that anyone was hiding it, on the O'Reilly Network: Weblogs page. The actual webpage for the proceedings is here. Unfortunately I'm not a member so I can't read the papers, a shame as some look very interesting.

The slides for the keynote are online though and their title, "Stop Thinking Outside the Box. There Is No Box.", reminds me of a similar, though I think more forceful, remark that I recently read. If you always have to think outside the box maybe the box is too small. What I take from that is that if you always have to work round, or outside, a broken, or narrow set of constraints or procedures perhaps you should address that larger problem and fix the process as well as solve the immediate problem.