Just about exactly five years ago, I wrote a goofy little program that walked through all of the CPAN and produced a CSV file telling me what was used to produce most dists. That is: it looked at the generated_by field in the META files and categorized them. Here’s what the first report, from April 11, 2010, looked like:

I spent last week in Berlin, at the 2015 Perl QA Hackathon. This is an annual event where a group of various programmers involved with the “CPAN toolchain” and closely related projects get together, hash out future plans, write code that is hard to get written in “free time,” and communicate in person the hard that is stuff to communicate over IRC and email.

At the Perl conference, YAPC::NA, there will be a ninety minute question and answer session with Larry Wall.

Once in a while, my daughter asks me to teach her programming. We’ve done a number of little things together, including some Python, some Scratch, and other things. When I was trying to think of what I enjoyed doing with computers around that age, one of the things I remembered was drawing. We did turtle graphics with Logo in my school, and it was nice to get instant and visual feedback of what the program did. I thought this seemed like a fun idea.

Saturday, 4th day of the Frost Moon, 937

[ update: I added a bit of an update at the end, in which I find that my fundamental worries were wrong, because the system is less convenient than I hoped! So it goes. ☹ I decided to post this anyway, because the thoughts were worth thinking, so maybe somebody else will find them interesting to see. Or not. Who even reads this thing? ]

Friday, 3rd day of the Frost Moon, 937

In 2007, I wrote code to generate RTF that syntax highlights code, using Vim’s syntax highlighting. I wrote about it in an earlier post or two. After that, I didn’t think about it much, apart from fixing a couple things once in a while or running it once every year or so.

This guest entry written by Breno, Rago’s player, who deserves great praise for doing so!

I wrote a todo for 2014, which I probably stopped thinking about roughly two weeks after writing it. Here’s a summary: