Geeks With Blogs
Jason Taylor Real World Azure Tales

I’ve realized as of late that I come home nearly every day (which, quite often is the next day) and do the following:

- Say something along the lines of “what a day!”

-Pour a big glass of a nice rye whiskey or a single malt scotch (Who am I, Jack Donaghy??)

-Get back to working

 

I’ve also realized that a good majority of my family and friends have zero idea of what I’m doing all day. So, I give you a generic “Day In the Life” of a software development manager or executive.

7:00 a.m.

Holy crap, it’s 7:00 a.m!

Make espresso

Run through shower like it’s a sprinkler in the front lawn in summer

Find the “nicest” tshirt and jeans (hey, I work at a startup) that don’t smell funny

Holy crap, I forgot about the kid!

Dress kid. Feed kid. Drop kid off at school.

Conference call with client / strategic partner / exec team on trip from school to work.

QA or Support team lead waiting for you in parking lot. Big problem waiting for you.

8:00 a.m.

Triage problem from QA / Support. Damage control.

Scan email – what’s urgent?

Sales guy corners you about some huge opportunity that you absolutely have to follow through on even though your product isn’t capable of what they want.

More coffee.

Stand-up meeting with Dev team. Did we not make any progress since yesterday??

9:00 a.m.

Open up Visual Studio, start back up with the prototype new feature you were working on.

9:05 a.m.

Dev team lead has an architecture problem they need your input on (stop for more coffee first)

10:00 a.m.

Go find the one UI / Design guy you have and drag him into the architecture discussion.

Wow, that was a lot of coffee. BATHROOM!

11:00 a.m.

Crap, still haven’t looked at the offshore QA results from last night’s build.

11:01 a.m.

Those test results have to wait, the VPN is down and the remote employees can’t work.

11:30 a.m.

Feel like I’m forgetting something…… check calendar

Double booked for lunch. One client meeting, one developer interview. GO TO CLIENT MEETING.

1:00 p.m.

Remember you have a production release that night.

Run around like a madman crossing T’s and dotting I’s, making sure prod release is ready to go. It is…. BUT. There’s always a but.

Last minute bug fix.

Regression test.

Pinky swear with QA lead that the build is good to go.

2:00 p.m.

Pull together production release notes.

Script database changes.

Do a final stage push to QA.

Triage remaining “hot” issues from this morning and get hot fixes started.

How will this impact the Sprint? Crap, we’re falling behind.

3:00 p.m.

Talk to boss. He has some awesome new idea.

Talk boss out of shifting gears completely.

School / Daycare calls. Kids is sick. SCRAMBLE FIGHTER JETS! IS THERE A GRANDMA AVAILABLE??????

3:45 p.m.

Look at dev environment and do some exploratory testing.

Developer is totally missing the mark on a requirement. Realign.

4:00 p.m.

Find some IDE / SDK / deployment environment issue that throws a monkey wrench in all plans.

Mitigate!!!

5:00 p.m.

World’s Greatest Executive Admin ordered dinner for you and the crew. And put beer in the fridge. Open-mouthed smile

Roll code to staging.

6:30 p.m.

VIP Swap to roll to prod. Cache doesn’t start. App down. MEDIC!!!!!!!!!!!!!!

8:00 p.m.

Prod rollout done, but found a bug (so much for pinky swear).

Triage – yep, have to roll a hot fix.

9:00 p.m.

Hotifx. Repeat last 3 hours.

Midnight

Home.

Said whiskey / scotch.

Update ALM system with release results. Prioritize next day.

1:00 a.m.

Coffee.

Life stuff…. don’t I have a mortgage payment to make or something?

2:00 a.m.

Big Bang Theory rerun.

7:00 a.m.

Repeat prior 24 hours (probably even on a Saturday).

Posted on Tuesday, January 29, 2013 7:21 PM | Back to top

Copyright © jasont | Powered by: GeeksWithBlogs.net