Stories
Slash Boxes
Comments
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 ]

pjf (2464)

pjf
  (email not shown publicly)
http://pjf.id.au/
AOL IM: miyuki3k (Add Buddy, Send Message)
Jabber: pjf@jabber.org

I run Perl Training Australia [perltraining.com.au].

I help with Melbourne Perl Mongers.

I spend an awful lot of time talking about Perl, and have had my picture in the Australian newspapers with a camel. That's rather scary.

Journal of pjf (2464)

Thursday August 09, 2007
02:14 AM

Open Source Developers Club

[ #34054 ]

Open Source Developers Club
Last night we had another Open Source Developers Club (OSDClub) meeting. I had volunteered my talk on An Illustrated History of Failure, and Simon Hildebrant had volunteered a talk on Selenium.

The night seemed to go well, but I can't help but be disappointed with my performance. I've been teaching all this week, and this is extremely time consuming. Waking up very early and then standing in front of a class for eight hours can sure be tiring, but that's not the real problem. After a full day of teaching, the last thing I want to be doing is spending an hour or more rehearsing my talk. I'd much rather be playing Pikmin (thanks Ian!), or mucking with technorati, or even watching commercial TV. This is especially the case when I've been teaching roughly every second week for the last two months.

I hold myself to a particularly high standard when it comes to presentations. Presenting is my job, and if I flub my lines or forget my slide order, then I'm extremely unhappy. For anyone who noticed my errors last night, I apologise. For anyone who didn't notice, thank-you. You're a great audience.

Simon's presentation last night was on testing the web with Selenium, which is an awesome tool, and which has lots of ways to plug into TAP and other testing frameworks. There were some interesting ideas being thrown around about how one can use Selenium to provide repeatable test cases for web applications, the same way that one would provide test cases when submitting a bug report for a traditional application.

The discussion got me thinking more about what if one finds a bug, but can't get it fixed. It's a good introduction to my next talk, which is Fixing the web with Greasemonkey .

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • i had hoped that simon would get a chance to talk more about selenium RC, but there was a lot of ground to cover and he did so very well.
  • So where are the History of Failure slides? It sounds interesting but the odds I'll be able to see you do this in person are vanishingly small. I don't want to have to wait decades just to perhaps be in the right place at the right time to get the information from your presentation.
    • Most of my presentations (including this one) are designed to be run with a real person presenting them. As an example, the failure talk is 150 slides in about 25 minutes, and a lot of those are pictures. It is not death by powerpoint. Unless you're hearing the talk, the pictures don't make (as much) sense, and you'll be disappointed. I don't want that.

      I'm currently looking at using SlideCasting [slideshare.net] to put the slides online synchronized with my audio. If I can get that working, then it will definitely

      • That's kind of unfortunate. A benefit of death by powerpoint is that the information is portable and doesn't require a human to perform.