How to write a Developer CV/Résumé that will get you hired

Slides from my LPW talk are now online!

How to write a Developer CV/Résumé that will get you hired.

Spotify and Perl Article

Sawyer X recently gave a talk in which he outlined that merely talking about the stuff we are doing helps promote perl (watch his talk here on youtube). I believe he is absolutely correct.

Mike Schilli is one person who I think is doing a fantastic job of this. He writes a Perl article each month in Linux Magazine which is available in print and electronic editions. Here in Australia, it's available in most newsagencies (which is where I tend to stand around reading it... and sometimes I buy it). I think thats some pretty solid reach.

His article this month uses Perl to talk to the Spotify API. Which to me, is a cool way to introduce people to Perl via something that is well known and external to Perl programming problems.

There is a pay wall and by way of disclaimer, I have no affiliation with the author, the magazine or Spotify (although I do have a Spotify premium account).

Inline Grant Progess

Greetings from PPW 2014.

David and I had a good week on Inline, but I had to cut it short to prepare for and attend this year's Pittsburgh Perl Workshop. I gave a mixed bag talk yesterday morning and the first topic was the Inline grant: https://www.youtube.com/watch?v=vDRLIjojlhg

You can read about our progress in the Week #3 report here: http://inline.ouistreet.com/

Don't forget to read the week #2 report as well, if you missed that last week.

The Silver Camel goes to ... Mark Keating

At the end of the London Perl Workshop this year, we presented Mark Keating with a Silver Camel, to acknowledge everything he has done, and continues to do, for the Perl community, and particularly the UK Perl community.

Here's Mark shortly after being presented with his Silver Camel:

Photo by Wendy G.A. van Dijk

In case you're not familiar with Mark:

  • He has been chief organiser of the London Perl Workshop since 2008
  • He is co-founder and co-leader of North-West England Perl Mongers
  • He's been involved in the Google Summer of Code
  • He's director and secretary of the enlightened perl organisation
  • He's chair of The Perl Foundation's marketing committee
  • He's been a key player in the scheme to send newbies to conferences
  • He's talked about Perl at non-Perl conferences
  • His and Matt's company (Shadowcat) are long-term supporters of Perl

Quick post-LPW roundup

I've just arrived back from the London Perl Workshop. Lots of very interesting stuff. A big thank you to the organizers! I especially liked:

There were some good lightning talks too. I liked:

For those of you who wanted a copy of my slides, they are on github.

Scratching an itch - interpolable HTTP Status constants

When working on larger web applications, I prefer to use HTTP::Status to provide human-readable constant names in the code. This is especially helpful for anything other than the common 200, 404 or 500 status codes.

But the constants exported by HTTP::Status are basically subs:

if ($response->code == HTTP_OK) { ... }

this is fine for most cases, but not when you want interpolable variables, for example, in hash keys.

So I wrote HTTP::Status::Constants. It's a simple wrapper around HTTP::Status that provides read-only scalar constants for the HTTP_* constants.

Tonight’s folly

I just realised that since the addition of /r, you can now write s!!!regex. Or s!!!regexp if you prefer.

What makes a parsing algorithm successful?

[ This is cross-posted by invitation, from its home on the Ocean of Awareness blog. ]

What makes a parsing algorithm successful? Two factors, I think. First, does the algorithm parse a workably-defined set of grammars in linear time? Second, does it allow the application to intervene in the parse with custom code? When parsing algorithms are compared, typically neither of these gets much attention. But the successful algorithms do one or the other.

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.