The CPAN PR Challenge is starting today. Latest polls have settled on 195 participants. People of all shapes and forms with different levels of Perl familiarity, experience, knowledge, and skill. Everyone seems excited and geared towards the challenge!
If you're participating, you might want to make use of the resources made available. I've tried to collect them here.
An interesting idea seems to be floating around the Internet ... creating a basic interactive website on how to contribute to a particular FLOSS project. After some noise on the Perl Monger Groups and Perl Propaganda lists I decided to help a few folks put together: http://whatcanidoforperl.org/ . You might have read something about it on Perl Weekly or not. If you have suggestions please create a ticket or better yet create a pull request here. Cheers!
In January more than 50 perl hackers will be starting the CPAN pull request challenge. They'll be randomly assigned a CPAN distribution and will have a month to submit at least one pull request.
Here I'll outline some things you can do to help the process, if you have distributions on CPAN, and are so inclined. Many of the particpants are relatively new to Perl, open source, and git(hub), so this is a way to help them "join in".
It's not too late to join in yourself — you can join at any time. Just email me: neil at bowers dot com.
Perhaps a misleading title. Seeing as this is not a political blog but a Perl one, I’m going to talk about method chaining, not worker’s unions.
Method chaining is the practice of consecutively calling methods on the return of a previous method. This comes in primarily two flavors. The first isn’t as common in Perl, though it is used extensively in Mojolicious, is when a method has nothing useful to return, it can return itself. This allows for say chaining setter methods $self->set_foo("FOO")->set_bar("baz"), or chaining related test methods
my $t = Test::Mojo->new;
$t->get_ok('/page/1/')
->status_is(200)
->text_like('#id' => qr/foo/);
While this is useful, it’s not my topic today. I’m going to talk about the more simple form, calling a method that returns an object, then calling a method on it, and so on.
I like to read at least a computer book every 2-3 months, that makes around six books per year. This year was a very unluky one for me, due to family and personal wealth problems and surgeries. However I'm back on the rail of reading computers book again, and Perl is the predominant one this year.
If you join the CPAN pull request challenge, then at the start of each month in 2015 you'll be emailed a (somewhat) randomly selected CPAN distribution. You'll have one month to submit at least one pull request. You don't have to be an experienced Perl programmer, CPAN author, or githubber. The goal is to help others, possibly learn something, and hopefully have a bit of fun.
If you want to sign up, email me (neil at bowers dot com), letting me know your github username and your PAUSE id, if you have one.
About the series: perlancar's 2014 Advent Calendar: Introduction to a selection of 24 modules which I published in 2014. Table of contents.
I'll close this series by mentioning that in August I created a few simple text-based games: Games::WordGuess, Games::Hangman, Games::ArrangeNumber. The reason I did this originally was because I got sick of playing word guess/hangman on Android with English words, and there doesn't seem to be any support for Indonesian version. So I found out about Games::Word::Wordlist::* modules on CPAN, uploaded a couple of Indonesian wordlists, and had to write a couple of games for using the wordlists too, since there happened to be no text-based hangman game or word guessing either on CPAN at that time).
I've always sucked at interface/interactive things though, so I welcome any patches/pull requests for improving the gameplay. I've got a couple more ideas for simple games, but lost interest after a few days, so those ideas will still remain in the backburner for now.
The past me is another person. Sometimes antagonist, sometimes friend, past me
(postaction?) had ideas, hopes, and dreams and developed some of them into
software that I and others use. Unfortunately, that asshole left bugs all
through the code for me to fix.
I can't blame him. Nobody's perfect, not even idealized/demonized copies of my
past self. But I do have to fix them, and deal with the messes he left.
Lucky for me, while he was writing buggy software, he left extensive notes for
me to use...
It's not that I don't see the utility for one-liners, it's just my own mindset that seems to prevent me to use them.
On one hand, I often explain to other (non-Perl) developers how useful can be a one liner, but on the other hand I tend not to use them even when I could.