Now I know why some programmers are so retentive about their code
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
I'm not retentive, I'm defensive. I always try and have a good, irrefutable, defense argument[1] for my code being clean. If I can't argue it's quality, it probably lacks it. [1] I am a law student as well.
I do not believe they are right who say that the defects of famous men should be ignored. I think it is better that we should know them. Then, though we are conscious of having faults as glaring as theirs, we can believe that that is no hindrance to our achieving also something of their virtues. - W. Somerset Maugham My New Blog
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
Why aren't you testing code before it is checked into the trunk? Also, why cant you just roll back the changes? Surely you have a test suite like nunit and ncover to help catch crap like this?
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
Why aren't you testing code before it is checked into the trunk? Also, why cant you just roll back the changes? Surely you have a test suite like nunit and ncover to help catch crap like this?
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
My code was tested. In fact it has been working for more than a month. It was the other guy that checked code that crashed without even testing it. But as I didn´t knew he had made changes I assumed it was a nasty bug on my part.
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
Gabriel Gibaut wrote:
And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
Accountability is just one of the benefits of source control.
If liberals are not traitors, their only fallback argument at this point is that they're really stupid. -Ann Coulter
-
My code was tested. In fact it has been working for more than a month. It was the other guy that checked code that crashed without even testing it. But as I didn´t knew he had made changes I assumed it was a nasty bug on my part.
Then roll back his changes. Or better yet, bring your boss to the monitor and show him the check in history and the guy's culprit code.
This statement was never false.
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
-
Past friday we had to deliver a release to upper management by the end of the day. At noon a coworker started to complain that he was getting random crashes on a module which I wrote 90% of it. (At first the crash only happened on his machine, but later started to happen on all of the devs machines) I stayed late trying to figure out what the problem was. I couldn´t find a reason. We couldn´t deliver the release. Today, when I found the bug (after spending the whole morning chasing it), it all became clear. -By friday morning my coworker wrote the missing 10% percent of the module. -He then started to have random crashes in the module. -He then assumed it was my error. -He then checked in his changes, even having random crashes, and propagated the bug to the rest of the team. -And as it was, to him, my bug, he left earlier on friday -Today he spent the whole morning surfing the web. -By five o´clock he asked me if i had found a solution to the bug. And even then, MY BOSS IS MAD AT ME BECAUSE HE THINKS I WAS THE ONE THAT INTRODUCED THE BUG...AAARGHHHH!!!!
Now you know what BLAME is for.
Please don't bother me... I'm hacking right now. Don't look at me like that - doesn't anybody remember what "hacking" really means? :sigh:
-
Now you know what BLAME is for.
Please don't bother me... I'm hacking right now. Don't look at me like that - doesn't anybody remember what "hacking" really means? :sigh:
Yes! Tomorrow I´m going to talk to my boss and tell him that I wasn´t the one that introduced the bug, that he can verify that on SourceSafe. I first doubted, but I figured out that why should I pay for someone´s else error when that someone else neither cared for the team nor for the product... Cheers Gabriel