Of course this would have to come up right before I go on vacation, right? My co-worker originally asked me if we could get together and talk specifics on Friday, and I agreed, but then apparently she and her colleague got too busy so it was pushed off to this week. And now Monday’s more than half gone and I haven’t heard from her yet, so who knows. Maybe she’ll want to sit down and hash things out first thing tomorrow morning; maybe it won’t happen this week at all, then I’ll be gone next week (which means I’m mentally half-checked out already anyway, which is why I won’t be chasing my co-worker down in the hallways reminding her about it), and by the time I get back it’ll be entirely forgotten. The major consolation, of course, is that it's not as though the project is going to be assigned to someone else in my absence if this week slips by; this worksite remains a one-programmer cibicle-town, and I am he. If it is still a going concern when I get back, then I reckon I'll get down to it then.
I do still get psyched when I get genuinely meaty development projects to work on around here, but I’ve also learned not to get my hopes up until there’s a concrete record of deliverables and deadlines that I can reference in my annual review time self-evaluation. So, once again I am hurrying up and waiting, with the nice bonus that if I hurry up and wait for nothing by week’s end, I get rewarded with a trip to the beach.