A typical monday

:-) Anthropologists love the mundane. They study the way people live day-to-day, the things we take for granted. So, here's a snapshot of my typical Monday:

4:54 am: Wake up and realize it's almost time to get up, but fall back asleep anyway, entering the depths of REM just in time for...

5am: Alarm goes off. Hit snooze bar for 9 minutes.

5:06am: Inexplicably wake-up, turn off alarm and arise from bed.

5:07am: Do what most people do immediately after getting up

5:10am: eat breakfast, watch the poor Lexington morning news anchors who've been up since 3am try to sound funny

5:30am: Spend next hour getting ready for work.

6:45: Banzai run to get to my 7am meeting. Pass carnage on I75 N.

7am meeting:
- Them: "Oh, we signed off the beta"
- Me: "Aren't there two gating issues still?"
- Them: "Oh, yes, but we signed-off the beta on time".

7:20am: Find out that our stability test from the past weekend blew up. Yep, it's Monday.

7:30am: Make coffee for entire floor.

8:30am: Officemate if I know if there are any doughnuts around. I reply: "If I knew where some doughnuts were, do you think I'd still be sitting here !?!"

9am: Receive surprisingly ironic phone call. Retrieve doughnut from the latest AYPT-cum-regular-employee. Mmm...doughnut.

9:30am: Daily stand-up meeting where programmers agree (like the cult that we are) that we have no idea why the stability test failed on Sunday. Agree that current project will never die. Coffee soothes the pain.

10:00am: Another daily stand-up meeting with different group of programmers, where we agree (like the cult that we are) that the best thing about their project is that it's not the other project that I work on. Manage to convince high ranking programmer on loan that overhauling our entire build process 2 weeks from Release Candidate is "A Bad Thing", because it has no upside other than "it ought to be that way".

10:30am -> 11:30 am: Monitor the email barrage between team and test group about why the stability test failed this weekend. Summary:

1) Developers: "Testers, your methodology sucks".
2) Testers: "Developers, your code sucks."

Ah, the checks-and-balances of Software development.

Comments

Post a Comment

Popular posts from this blog

Review: The Southeast Christian Church Easter Pageant

Easter Pageant?! What is this, amateur hour? Who cares about some piddly church passion play? What's next, "Best Little Christmas Pageant Ever"? How's this for Piddly: Two professional composers, a 9000 seat auditorium, 75,000 tickets over a month-long run, a 300 person chorous, two IMAX-size video screens. Traditionally, Southeast's Easter Pageant has been the biggest theatrical production in Louisville. They took a year off to retool and rework it, comissioning a rework from the ground up. Whereas the previous iteration had been a "cast of thousands" broadway-style production, they wanted something...different. Hoo-boy, it was different. Let's talk about "theatre" that is 1/2 movie, 1/2 live action. Apparently, they shot it at a quarry during last year's drought, and it looks pretty good. Still, I didn't like it...distracting and interrupts the flow. Likes It's not the same program they've put on for...
Read more

Rant On getting smacked down...

Image
So, you live in an organization for 10 years, and you acquire a certain rep. A reputation as a maverick, a guy who's not too wrapped-up in procedure, kowtow'ing, and career. You've said some things in meetings that were career-limiting, but damn it, they were the RIGHT THINGS. Sure, you broke into someones computer once to get their hard drive so you could deliver the code she REFUSED TO CHECK IN before going on vacation. Sure, you telnet'd in to a running test server to see if your hack worked and could save everyone working the weekend (it didn't, you hosed the test run, and you worked round the clock that weekend). Sure, you've slapped your head at stupidity (both in others and your own), and welcome anyone who'll do the same. However, 10 years, several promotions, two kids, a mortgage, and a car payment tend to make you forget who you are. For one sparkling moment this morning, you remembered. You asked an innocent email question last night to a te...
Read more

"Spiderman 3"...WHY?!

Spiderman 3 is a boring mess. The story is a mishmash of plotlines, centering around the three (yes, THREE) villains -- Goblin Jr., Sandman, and Venom. Overlong, the film languishes in its many plots, opening with Spidey wounding his friend Harry Osborne, now the reborn Green Goblin, then sauntering to the Sandman, and the Venom super-spidey suit. There's no discernible momentum until Mary Jane calls it quits with Peter, who's been quite an ass, though she herself has been a needy baggage for 4 reels. In any case, this sets off a battle between Harry and Peter, and FINALLY some action. Had the movie begun here and run for a tight 85 minutes, cutting out the Sandman character altogether, it would've been awesome. As it stands, this bloated ($300 million) mess has probably killed its franchise. * * * Also, I need to remind myself that I get sick if I eat too much popcorn.
Read more