Didn’t You get that Memo?
- 0
- Add a Comment
Sunday at 3AM, I finished some bugfixes and pushed code to test. Apparently Test was unprepared for it and flew off the handle as a result.
Tester Lead: “There was a code drop at 3 AM last night!”
Dev Mgr: “So?”
Tester Lead: “Don’t you think that’s a little unusual?”
Dev Mgr: “Well, try as I might, I just can’t get these guys to stop working.”
So my boss comes over and asks me about it…
Dev Mgr: “There was a code drop at 3 AM last night?”
Me: “Yep.”
Dev Mgr: “Why?”
Me: “That’s when I got done.”
Based on the fact that I didn’t do these things at previous jobs, I suppose it would be safe to call me “Money-motivated”. Anyway, these events reminded me of a similar event that happend last week:
Test Lead: “I can’t get this new code to work. It works fine on the old code.”
Me: “So it works fine up until you overwrite the old stuff with the new stuff? Did you get the data too?”
Test Lead: “Yes. I just can’t figure this out. The data goes missing when I put the new stuff in.”
Me: “Yeah, overwriting the database will do that.”
Test Lead: “Wha what?”
Me: “When you overwrote the database, you’d lose the data from the previous version as it has been cleared for next test phase.”
Test Lead: “Why would I overwrite the database?”
Me: “Because of the new database drop.”
Test Lead: “I didn’t know there was a database drop!”
Me: (Pause for effect) “There was a database drop.”
