Typical

[lokheed]

The message came just before 3pm.  There was a problem at work and Sara really needed to talk to the school principal, and could I possibly get Ben off the bus.  Ever the optimist, I figured I'd zip over, take him for some fries, bring him home, and that Sara would arrive 5ish.  I'd be back home by 5:30, no harm no foul.  Naturally that didn't happen.

Sara didn't even call me until after 6pm.  I didn't get home until after 7:30.  Apparently Sara's discussion with the principal turned into an impromptu performance review that did not go especially well.  I just don't even know where to go with that.

On the upside:  I started the day with five high priority bugs to fix, the ones that absolutely have to make it into this release.  I ended the day with one.  Oh, I still have plenty of other bugs.  But anything past those five are just gravy.  At the rate I am working, I should be able to fit another half dozen bug fixes into this release.  So that's pretty cool.

Comments

[wingedelf.livejournal.com]

Yep. Graaaaaaaavy. And i was done by 4:15 this afternoon. Being efficient and knowing the issues helps amazingly.

[lokheed.livejournal.com]

Being efficient helps? Geez. Here I thought the key was to have everything tracked in Project and to work in tiger teams in a bullpen environment so that you can move around your user stories to rapidly iterate to the properly refactored resolution.

[wingedelf.livejournal.com]

Well, that too, except not so much so when real work is involved. As long as it's all theoretical, buzzwords work just fine.