When I transitioned from using Perl as a systems engineer, systems administrator ... etc. etc. to working as a full-time developer I was upset to discover the local Perl mongers group fizzled out a long time ago. The last post on the mailing list was about free training from Erols.com (remember that company??? WOW!?) Needless to say that's some old stuff ...
I was psyched to get things going again so I set out to figure out how to do things the proper way and assume the role as the group organizer. For those of you in a similar position I hope this post helps you!
The first thing I did was post to the mailing list and through the other communications channels to determine if anyone was still lurking.
After confirming there weren't any lurkers or other people with an interest in resurrecting the group that could help me, I looked at the Perl Mongers FAQ which pointed me to the #mongers IRC channel on irc.perl.org.
In response to sending out the Perl Weekly I've already received two e-mails from people asking if I got information about
DC-Baltimore Perl Worksop
that will take place on April 11. Presumably they wanted us to include it in the Perl Weekly newsletter.
The fact that people reach out to the editors of the Perl Weekly is lightyears better than people who just expect us to know about every event and to promote them, but we cannot do much with the events without some news.
I pointed both of them to the list of Perl Events where the DCBPW is already listed and I told both of them that if they would like to promote the workshop (which is a very positive thing by itself), and if they would like it to be included in the Perl Weekly, they need to generate some news item.
It does not need to be earth shattering, just something we can use as an excuse to talk about the event.
I put together a page on promoting Perl events, in case you need ideas what to write about.
Or you can just write about something else and link to the event as I just did above.
On Thursday, 19th March 2015 I uploaded my 366th consecutive release to CPAN. To most that may well be "meh, whatever!", but for me it has been an exhausting yet fulfilling exercise. The last 60 days though, were undoubtably the hardest to achieve.
I’ve upgraded Facebook::Graph to work with the new Facebook v2 Graph API. For those of you who’ve been asking me to do this, here you go! For those of you using Facebook::Graph and didn’t ask me, you should know that Facebook will be discontinuing the Graph v1 API April 30th. If you don’t upgrade to this version of the module, then your apps will stop working.
[From my blog.]
In February I had the pleasure and honor of releasing the latest development version of the Perl 5 language interpreter: 5.21.9. Here are my notes on the work and on the epigraph I've chosen.
Note: due to positive feedback on the post and at a client, I've released DBIx::Class::Report to the CPAN. You can read the original announcement here.
An offhand tweet about Perl 6, inspired by this ycombinator response, led to what I think is my most popular tweet of all time (which, compared to many others, isn't that big of a deal):
But I was also asked what the heck the code is doing, so let me walk you through it.
Thanks to a generous venue offer from Bloomberg, L.P., I am pleased to announce the Second New York City Perl Hackathon, to be held Saturday, May 02, 2015 ( 10:00 am - 5:00 pm )
731 Lexington Ave ( between East 58 & 59 Sts )
New York, NY 10022
This hackathon will have 2 different participant roles:
1- Project Leader : Participant has a project he/she want other Developers to hack on.
2- Developer : Participant signs up to work on one or several projects lead by a Project Leader.
For everyone who is considering to participate please hold the date and think about which role you will play ( Project Leader | Developer ) in this hackathon.
There is a two-part sign-up for this event:
(1) Use this meetup.com page to register for the event. You must provide your first name and last name for access to the venue and must bring photo ID to the venue on Hackathon day.
(2) Use the New York Perl Hackathon wiki page to sign up to work on particular projects on Hackathon Day. Be sure to read: Getting Ready for the Hackthon and Projects .
I was working on some POD processing code when I went down the rabbit hole finding the proper module for handling POD files and created a draft just by listing a bunch of
modules for POD processing
But then this question popped up again:
I am probably missing something fundamental, but I don't understand why are there no semantic pod markups? I mean such as =method , =function, =attribute etc. Instead of that we use =head2, =head3, =item in a rather arbitrary way. Which means it is harder to display them in a similar way across modules.
Alberto Simões pointed me to Pod::Weaver which collects =method and =attr tags and puts them under =head1 or =head2 tags, but that's just made me wonder even more.