I mean, they’re not one-liners. They’re full programs. They just do something really really simple.

…not really. I still really like using GitHub, and (obviously) they do much more than I could churn out in a weekend, let alone an hour. Also, I used Perl.

First off, my slides. Whenever I give a presentation, someone will ask me whether the slides will go online. Sometimes they do, and sometimes they don’t. This year, I gave three presentations: one on Git, one on some new email libraries, and one on Rx. The email slides will probably go online soon. I’m not sure the other two will.

I’m trying to keep up to date with what’s going on in the Dungeons & Dragons world. I think the fourth edition rules are nice and easy to use. On those occasions where I encounter a rule I don’t know well, I can guess and when I look into the rules later, it usually ends up being easy to remember for next time. I’m looking forward to seeing the new rules for psionics. I like the stuff they’re doing with hybrid classes to introduce something more like old style multiclassing.

Let me start off by reassuring you: I’m not going to go on and on about how everyone needs to stop using Email::Send forever. I will stop once nobody is using it anymore.

If you don’t use LiquidPlanner, this post might be incomprehensible and/or boring. I’m writing it in part just to help form my own ideas.

I was long at least tangentially involved in the development of the Email:: namespace’s early code. I talked with Casey West often when he was working on Email::MIME and Email::Send. Once I started working at Pobox, though, my email needs became much more serious.

Wow.

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: