I’m learning Forth. So far, so good. Even if I don’t end up using it for much, maybe it will make me a better dc user.

While hacking on a large system at work, months ago, I spent about a day looking at every URI router or request dispatcher on the CPAN. That day, I was feeling really unhappy with all of them. They all seemed just fine, if you were starting from scratch and had no particular vested interest in how your router worked. For me, though, none of them quite cut it. I decided it wasn’t worth trying to change the design for the rest of the application. I would just write a new, bespoke router.

I thought I’d post my travel plans, in case anybody else is by some strange coincidence on my flights and wants to chat or hack in flight, or ride the MAX together, or whatever.

Every year at YAPC::NA, there is a conference dinner where I end up sitting with some people I know and some people I don’t. We talk about the conference, and Perl, and our jobs, and the city, and so on. Once we’re part all the introductory small talk, the auction starts and we spend two hours waiting for it to stop. Once it’s over, we leave.

Earlier today, I tweeted:

What is Moose?

First, I feel like I should make something really clear: I like D&D 4E. I think it has a lot of good ideas in its rules, I don’t think its initial expression necessarily represents the videogamification of Dungeons and Dragons, and I don’t agree with the objection that “it isn’t D&D anymore” just because it differs (wildly) from both the mechanics and feel of the original game. I have a lot of good feelings about 4E and a lot of good that I could say about it.

Years and years ago, I got a fortune cookie that told me:

In June, the Sixth Edition of JavaScript: The Definitive Guide went into the “Rough Cuts” program. That means you can give O’Reilly (really the Safari Books Online) $25 up front to get access to downloadable drafts of the book in PDF and other formats. When the print version shipped, you’re automatically charged another $25 and shipped a print copy. Because we’ve always found this book, “The Rhino,” such a great resource, we decided to sign up for the Rough Cuts edition of it.

Part of my work at the QA Hackathon led to making it quite a lot easier to test minicpan. I’m pretty happy with that, and got to work writing tests. Once I had the basic “mirroring works” tests written, I wanted to have a quick look at testing logging. Unfortunately, it turned out that logging was a big mess.