I’ve always liked Email::MIME::Kit, and I just keep liking it more. This week, I wrote a Markdown-based assembler class. Assemblers turn the templates, stash, and other configuration into the MIME message. Right now, they’re sort of a mess, but they’re really, really useful.

I got this message:

Clearly there is something to the notion of star power. I’m half-watching the movie Lifeforce for the first time and thought, “Boy, that guy really reminds me of Mr. Deltoid, a minor character in a movie I haven’t seen for 15 years or so.”

After reading perlpodspec a few times and trying to reconcile all my hopes for my Pod-munging tools with the pretty restrictive rules of the spec, I have come to imagine Pod as a nested set of layers of specification, almost like the skin on an onion. Go figure.

I wonder how much time I’ve lost in my continual worrying about productivity software. Probably not enough to offset the gains I’ve made by finding things I like. OmniFocus still stores most of my personal todos, index cards still get a lot of my random notes, but LiquidPlanner remains my absolute favorite project planning tool for work.

I’ve begun work on my Pod-munging grant. My first real task has been reviewing perlpodspec, which is the most useful document one can read about writing a Pod parser. It’s a bit unstructured, but for the most part it’s clear, unambiguous, and useful.

Oh. Actually, Pod::Weaver is already on the CPAN. It’s just not all that useful yet. I had been using it as part of Dist::Zilla for a while, but it needed more work to be useful for my applications. Some of it was design work and some of it was implementation work, and rather than sort it all out, I took my early, crappy proof of concept work and released it as its own thing, PodPurler. It wasn’t extensible, tested, or… well, it wasn’t very good. It just happened to do what I needed.

One of the reasons I was keen to use GitHub for hosting controlled files at work was because of the slick chrome that GitHub puts on a lot of Git operations. It meant that some of our less technical users could still benefit from using a DVCS without having to understand a lot about remotes or merging. Unfortunately, it turns out that the most important piece of this chrome is totally unsuitable for use by non-technical users.

If I were going to was introspective, I’d say that one of my best and worst qualities is my love of designing something for ages before building it. I think it tends to make my end product better, but it also means that the product languishes. Right now, that’s the state of Email::Sender::Simple.