Posts by Yanick Champoux
As it was my very first YAPC, I stuffed my schedule as if I were a child left alone in a bakery and the talks were cakes. Consequently, I ended up booked solid from 10am to 6pm for all of the three days of the conference. Next time, I will probably go a little easier on the talks and give myself more room to attend hackatons, BOFs and whatnots. But for a first time? Walking the talks was the way to go, both to get a feeling of the conference and to take advantage of the occasion and connect all the Perl big names with their wetware implementations.
Boys and girls, please make yourself comfortable. Sit back, clip your seatbelt, and relax as we ready ourselves to take the scenic route to YAPC. I’ll try to stick to a semi-chronological order, which means that I will begin at the beginning. Maybe not the beginning beginning — my youth was a fairly uneventful and boring one — but a beginning that provides both scope and a springboard to this odyssey.
Thanks to Pythian’s philosophy of keeping their employees on the bleeding edge of technology, at the end of this month I’ll be crossing the American borders to join the YAPC::NA festivities. Am I thrilled? Ooooh heck yeah, I sure am. I looked at the list of talks and divided them into two groups, talks I want to see, and talks I really, want to see. Here is what my own personal schedule tentatively looks like:
The best way to get a feel for a module is to work with it, I decided to try my hand at a small, unassuming maze game. For the maze creation itself, I used Games::Maze, and with that out of the way, the resulting program turned out to be quite simple, have a look.
Since writing a blog entry sorely to talk about a software release bearing my name would be slightly… ah… self-serving (and we couldn’t have that in a blog, now, could we?), I thought to expand a little bit on the topic and discuss why I am contributing to other peoples’ modules, and how I usually go about it.
When I begin to work with a module, most of the time what I do is to look at its pod, and copy the code in the synopsis that I’ll use as a a baseline. I’m pretty sure there’s already a better tool to do it somewhere in CPAN, here’s my little podsyn script that does all the hard work for me.
This Thursday, I’ll be presenting at the Ottawa Valley SAGE meeting. The topic of the talk will be Perl for Sysadmins, and I’ll try to sell to the audience how Perl can make their lives much, much easier.
With Dist::Zilla, so far I was manually setting up the new version number in the dist.ini of my distributions. But, as I’m a lazy, lazy man, automating the process was still at the back of my mind. Well, I finally found the time to work on this. The result is Dist::Zilla::Plugin::Author::YANICK::NextSemanticVersion, which currently lives in the Dist::Zilla::PluginBundle::YANICK distribution (and, of course, in its GitHub repository).
A few days ago, had you asked me one big plus of Catalyst over Dancer, I would have said “chained actions”. Chained actions allow to split the logic underlaying an uri into smaller components associated with its segments. A very neat, DRY-friendly ways of doing things. Have a look.
All the tools you need to write a Dancer plugin are contained in he helper module Dancer::Plugin. To invoke them, you just need to ‘use’ Dancer::Plugin within your module — all the inheritance stuff is taken care of behind the curtain