[filk] Filk: The Twelve Days of Code Freeze

From: Chuck & Maura <mythosmanor at hotmail.com>
Date: Mon, 10 Dec 2001 12:58:07 -0800

Forget if I forwarded this to the group or not. Just a stupic techie filk I wrote when working at a tester for a seattle area software house (dot.com trying to find a non dot.com use for their technology) Some of these items make reference to things that really happened (8 hours of triage). and OR is short for Object Repository (having it fail was bad..) ----- Original Message -----
From: me
To: folks where I worked
Sent: Friday, September 14, 2001 2:52 PM Subject: Humor: The Twelve Days of Code Freeze

The Twelve Days of Code Freeze

    (To the tune of Twelve Days of Christmas)

 On the First Day of Code Freeze the developers gave to me..   A new Fork in the Code Tree

On the Second day of Code Freeze the developers gave to me  Two Java Errors
 and a new Fork in the Code Tree

On the Third day of Code Freeze the developers gave to me  Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Fourth day of Code Freeze the developers gave to me  Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Fifth day of Code Freeze the developers gave to me  F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Sixth day of Code Freeze the developers gave to me  Six Paths a Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Seventh day of Code Freeze the developers gave to me  Seven Builds a-Breaking
 Six Paths a-Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Eighth day of Code Freeze the developers gave to me  Eight Hours of Triage
 Seven Builds a-Breaking
 Six Paths a Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Ninth day of Code Freeze the developers gave to me  Nine PM's Stressing
 Eight Hours of Triage
 Seven Builds a-Breaking
 Six Paths a-Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Tenth day of Code Freeze the developers gave to me  Ten Tests a-Failing
 Nine PM's Stressing
 Eight Hours of Triage
 Seven Builds a-Breaking
 Six Paths a-Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Eleventh day of Code Freeze the developers gave to me  Eleven Threads a-Dying
 Ten Tests a-Failing
 Nine PM's Stressing
 Eight Hours of Triage
 Seven Builds a-Breaking
 Six Paths a-Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree

On the Twelfth day of Code Freeze the developers gave to me  Twelve New Code Checkins
 Eleven Threads a-Dying
 Ten Tests a-Failing
 Nine PM's Stressing
 Eight Hours of Triage
 Seven Builds a-Breaking
 Six Paths a-Changing
 F I V E B L O C K I N G B U G S
 Four Null Pointers
 Three OR Failures
 Two Java Errors
 and a new Fork in the Code Tree !

 Inspired by the agenda item "(this is the 11 threads a-dying issue)" in today's release coordination meeting..  Yes, I'm a sick puppy...

---

Chuck van der Linden
Software QA Automation Engineer

---

Received on 12/10/01