«

»

Phantom bugs

You know, I was going to post pictures of cake for today’s post. No shit. However, I had a hard day at work today, so I just need to unload a little bit.

We’re currently in a period where projects are under test before going live. The testing was supposed to end today, but we were stuck figuring out solutions to one or two bugs. One in particular has been rather nasty in that none of us in house could produce the bug. People on the client end were able to produce the problem, but only once per computer, after which it could never be generated again. Most of us dealing with the bug spent many hours trying to find a viable solution, but nothing worked. A few of us stayed for about 10.5 hours from just trying to provide support. We were completely worn out.

As I was packing up for the night, someone not working on the release commented about how great it was to work on such tasks. I was genuinely puzzled when I got that comment. He continued to say that time flies and then oops, all of a sudden we’ve banked 2-3 hours overtime. I just laughed at it, but on the inside I was still dumbfounded.

Why should I consider having to stay overtime a good thing?
Why should I be pleased when I haven’t been able to solve this phantom issue?
Why is it supposedly an easy period when I’m expending so much mental energy just brainstorming for solutions?

I don’t know, man. I couldn’t help but feel that our priorities were really different. It’s late, and I’m still kind of down about today’s failure. I’ll be in tomorrow for 8 in the morning. I hope that we can make better progress tomorrow with a fresh set of eyes.



Possibly related posts:

  1. After hours
  2. Compulsion to stay

About the author

Jay

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Switch to our mobile site