We’re using Github issues for all of our projects, but I still like Remember The Milk as the interface for deciding what I need to work on next. It would be neat if the two worked together.

An issue assigned to me in Github would produce a new inbox task in Remember The Milk (if one didn’t already exist with the issue in the URL field). I could then list, prioritize, and give a due date as needed. Completing the task in Remember The Milk would complete the issue in Github (and vice versa).

Plans for today and tomorrow: running in Forest Park, picking up shelves to finish the entryway, designing the blag, hiking in the Gorge, getting a new book at Powell’s, making nograinola, and/or seeing a movie. In no particular order. The best type of weekend.

On Alaska 388 for a quick trip to San Francisco to meet Tom and Joe for the first time. Excited for what’s ahead, both the future and the conversations we get to have for the next 24 hours. With any luck, I’ll be back in Portland tomorrow by 7 pm for the PDXWP developer meetup.

An idea: Use creation of WP_Error objects as a way of tracking application exceptions. If WP_Error had an action in the __construct() method, you could easily error_log() WP_Error codes and messages.

Can someone tell me why this is a bad idea (other than exploding your error log), or whether there’s a better approach?

Mind is bursting with ideas of what the product could be, how we can identify and match the needs of users, and how to build it out. Loving the new challenge.

Sign I’m growing up: I was kicked out of the condo this evening for Leah’s book group.

I say it’s an excuse to drink wine. She says I’m being sexist, but she didn’t explain why having an excuse to drink wine is a bad thing.