[This is a post in a new, probably long-ass, series. I do not promise that the next post in the series will be next week. Just that I will eventually finish it, someday. Unless I get hit by a bus.]
So, last time I laid out my dissatisfaction with existing date modules and described what I was looking for in a feature set out of a potential new module. Well, a feature set is a good thing to have, but it’s a lower-level view. Let’s take a step back and try to pin down exactly what need I want my date module to satisfy; that is, what niche am I hoping it it will fill? When you’re looking for a date module to solve a particular problem, which problems will lead you to this one?1
[This is the first post in a new, probably long-ass, series. I do not promise that the next post in the series will be next week. Just that I will eventually finish it, someday. Unless I get hit by a bus.]
The topic arose at
$work recently: what do the cool kids use for dates these days? Our sysadmin was looking for a simple way to get “tomorrow.” Of course, the cool kids are theoretically using DateTime, right? So, how do we get “tomorrow” out of DateTime? The answer came back in our chat room:
Well, okay ... that would work. But it’s not exactly what I’d call “easy.”
Last week I formulated an interesting problem in text processing while working on one of my hobbies. Since I was only able to devote an hour or two here and there, it took me a few days to get the solution up and running, which indicated to me that it wasn’t as simple as I’d thought it would be at first. And since “not simple” often means “interesting,” I thought I’d share it here with you. (Note that I don’t claim this is the best solution, or the most efficient, or the most elegant. I’m perfectly happy to receive suggestions for improvement if you’re so inclined.)
The exact application isn’t important, 1 so let’s just look at the general parameters. There’s a series of cards, and each card has one or more powers on it (where a “power” in this case just means a block of text). I have a file with all the powers in it, and a little script to help me search for patterns within and across the powers. Let’s assume the powers come in, one per line, like so:
Name of Card / Name of Power : Description text of power.
(They’re not actually formatted like that in the file, but I have another script that transforms them into this.) So my analyze script lets me search for a given regex (Perl-style, natch) and prints a nice summary of the results, like so:2
This year I attended my fourth YAPC. As always, here are my thoughts. This time around, let’s start with ...
THINGS I LEARNED AT YAPC:
(Wow, has it really been almost 6 months since I last posted here? Man, I’m slacking ...)
A while back, I decided to play with Dist::Zilla, and one of the first things I decided to do was make my own plugin bundle.1 Now, if you don’t know what a plugin bundle is ... well, that’s a bit above and beyond the scope of this article.2 Suffice it to say that, if you want to get the most of out DZ, you want to create your own plugin bundle. (And, if you don’t want to do that, then you probably want to be using something simpler than DZ, like Dist::Milla or Minilla or Zilla::Dist.)
So I created one a long time ago but then I never did much with it. I personally don’t have enough CPAN distros to juggle to make spending a lot of time fiddling with DZ a priority. But lately I’ve decided I want to get back into it. So I started out by installing the latest version I’d put out on CPAN.
Well, trying to install it, anyway.