





9:00 A.M. Eat breakfast in cubicle/office

9:30 A.M. Attend the daily Scrum meeting

9:31 A.M. Immediately zone out after stating my progress report and fantasize about a fight between a ninja and a pirate for the remaining duration

10:00 A.M. Be visited by fellow developer Steve, who tells you how fellow developer Bob doesn’t have a clue about his job

10:30 A.M. Check out latest source code and begin reviewing the code introduced by the junior developers

10:45 A.M. Weep

10:50 A.M. Fix the mistakes of your junior developers

11:30 A.M. Be visited by fellow developer Bob, who tells you how fellow developer Steve is an imbecile

12:00 P.M. Prepare to eat lunch when a production issue suddenly strikes

12:30 P.M. Attempt to fix the production issue while hungry and in panic, resulting in only more unfolding disasters

2:00 P.M. Eat lunch finally and bitterly

3:00 P.M. Go to meeting about upcoming project A

3:10 P.M. Project manager Mark interrupts the meeting to talk about his new project B and to point out that project A has many flaws

3:20 P.M. Everyone argues at the meeting and threatens to murder each others’ families

3:50 P.M. The meeting is postponed until the next day

4:00 P.M. Finally start to write some code for your own project

5:00 P.M. Your boss asks you to come into his office for a conference call

5:15 P.M. Your boss has a conversation with you, asking if there any obstacles that are delaying your portion of the current project

6:00 P.M. Leave work

7:00 P.M. Prepare to eat a warm dinner when another production issue forces you to remotely log into your system from home

8:30 P.M. Eat a cold dinner between clenched teeth

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.