3:37 pm: for some reason they are running two sessions instead of three right now, meaning they are both standing room only. The guy talking about social networks is beating around the bush. Your reporter grows tired…
3:09 pm: now a talk about legacy apps. Unfortunately I am having trouble understanding the speaker, which seems almost an apt metaphor for trying to understand the code in inherited legacy apps.
2:36 pm: all in all a pretty balanced, though bawdy, talk by Matt Trout. My final impression is that Perl 5 is reaching a critical mass and we need Perl 6 sooner than later, at least if the quest for good standards is to reach any kind of fulfillment.
2:20 pm: he’s pushing Catalyst (another web application framework) now. Ah… it’s his project. It all makes sense now. :)
2:17 pm: now he is dissing on CGI::Application and how the plugins are a bit of a “free for all”.
2:07 pm: another meme kicked off in “The Mythical Man-Month”: Second-System Effect.
2:04 pm: Matt Trout is giving a pretty funny and philosophical talk.
1:57 pm: now attending a session entitled “Catching a ::STD” which is a pun on the Perl 6 standards doc (well actually a module) maintained by Larry.
1:51 pm: Recession alert: there are some very talented unemployed people here.
1:49 pm: I’m probably crusty or resistant, but, it seems like POE and Moose are sledgehammers for finishing nails as far as what I am needing. These things were designed with large systems in mind.
1:21 pm: now attending a session on POE::Filters.
11:31 am: second recommendation for Devel::NYTProf this conference. I think I might check this out. Project was started by the New York Times and is now maintained by Tim Bunce.
11:26 am: this is turning into a Moose session.
11:19 am: now a talk about XML::Toolkit.
11:02 am: Jim makes the point that you can’t program the office workflow without support from above. Grassroots workflow efforts don’t work. I’ve found that to be true as well– adoption needs to be forced for certain applications to work.
10:50 am: not sure that Workflow.pm is for me, I’d probably just roll my own. None of these scenarios are tough to code on their own, IMHO. Maybe I’m missing something.
10:36 am: finally, code!
10:34 am: still no code. This guy is obviously smart and coping as well as he can in some hellish corporate sweatshop. Code though? He’s probably been told not to show code in presentations by his business people.
10:26 am: Jim Brandt is being descriptive about business workflows but I want to see the code.
10:18 am: The email talk is over; onto a talk about business process management with Workflow.pm. This will either be eye opening or completely off base.
10:14 am: I wonder if I will remember this presentation after being burned by email two or three more times and finally take this guy’s advice.
10:10 am: now he’s selling me on Email::MIME::Kit. We’ll see, I guess. I am about to open the email can of worms again on the SSR application.
10:05 am: starting to fear that I shouldn’t be using Email::Send. Ricardo is selling me on Email::Sender.
9:57 am: Ricardo Signes is talking about his on and off romance with handling email as a Perl programmer. Now he is mentioning some of the common modules that are used.
9:54 am: just got out of chromatic’s standing-room-only talk on “Modern Perl”, which is an effort to make Perl 5 the best it can be. They added another talk on the topic due to the interest.