A while ago, someone directed me to Obsidian Portal. It’s a website where you can collaboratively develop an RPG campaign. A camapign has a wiki, PC and NPC tracking, an adventure (b)log, an item tracker, a map archive, and forums. There might be some other stuff, too.

Lately, I have a lot going on. I think I need to recalibrate my “very busy” alert, because I feel like it’s been going off for months, now. Still, things are okay. Here’s a bit of a dump on some things I’m working on or should be working on.

On the recommendation of a friend, I tried out the Charles HTTP proxy for debugging… web stuff. It’s nagware, and the nagging is really annoying. Despite that, it was obvious within the first two hours that I was going to buy it. It made it very, very simple to diagnose a number of problems that Firebug and Safari could not sort out. (They both seem to clear their logs fairly aggressively during redirection, for one thing.)

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.