Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

barbie (2653)

  reversethis-{ku. ... m} {ta} {eibrab}

Leader of [] and a CPAN author []. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [] and the QA Hackathon [] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Memoirs of a Roadie []
CPAN Testers Reports []
YAPC Conference Surveys []
QA Hackathon []

Journal of barbie (2653)

Thursday June 19, 2003
08:54 AM

Last nights talk

[ #12947 ] had a technical talk last night. Lots of good stuff, tons of cool stuff (mainly from Rich), some interesting stuff and some broken thoughts (mainly from me).

Due to my lack to time given to prepare notes and spell check, there were a few errors in my slides, along with a bit of a flow problem in a couple. Having time to run through them before hand is always a good thing. I had to drop my third talk, More LWP, as I just didn't have the time to write it. We managed to talk for two hours though.

Rich's two talks went down very well, especially the Device::Ericsson::AccessoryMenu one. Complete with XBlast competition via mobile phone :) Siesta looks like it's coming along well, they just need to finish it now.

JJ's talk on the R in Perl was well done, including the bit of how to annoy non-Perl programmers.

My talks prompted some discussion and ideas, which was the main reason I wanted to do them, so I got the result I wanted, even though I could have done with presenting them a bit better. Still food for thought and perhaps once I've had time to look deeper into the CGI Parameters Validation talk I might be able to present it to or even a YAPC next year. We'll see.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.