not good. really not good. not good at all.
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
TorstenH. wrote:
Seems like I'll have to be the unlucky messenger to break the news
Either you will be blamed or appreciated. Blaming, for hiding this breaking news. Appreciation, for taking stand at least to resolve it now.
Regards, Hiren. -"I don't know, I don't care, and it doesn't make any difference".
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
No biggie. Just report it, you are a professional. Check and review your procedures to improve them (better code review, unit tests, black box testing, ... ) and limit the possibility of that happening in the future.
Watched code never compiles.
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
At least you found it and as long as it can be fixed without much ado you're a rock star.
VS2010/Atmel Studio 6.0 ToDo Manager Extension
Version 3.0 now available. There is no place like 127.0.0.1 -
no work around. I checked on multiple systems in the production area (we are also selling hardware). It's in every installation...
regards Torsten When I'm not working
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
-
At least you found it and as long as it can be fixed without much ado you're a rock star.
VS2010/Atmel Studio 6.0 ToDo Manager Extension
Version 3.0 now available. There is no place like 127.0.0.1should be fixable. I'm just amazed that no one yet saw it. It's totally obvious!
regards Torsten When I'm not working
-
No biggie. Just report it, you are a professional. Check and review your procedures to improve them (better code review, unit tests, black box testing, ... ) and limit the possibility of that happening in the future.
Watched code never compiles.
Yepp, we need to. But as long as I don't change something nobody does. It's a pretty lame procedure to change things. Lot of the guys are working here since 20 or more years. They don't move much...
regards Torsten When I'm not working
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
As you say no one has noticed, go to management with the reason no one noticed, what the bug is and what the solution will be to make sure your derriere is not left visible.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Err no. If you change code, it must be tested.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
The lesson to be taken out of this is what procedures do you need to put in place to prevent an occurrence like this happening again. If the bug is that big, it should be squeaky bottom time for your test team. They will be the ones who gave to explain why they never saw it.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
NO! Naughty boy! Unauthorised and unrecorded changes in production software? Ouch! Shove it up the food chain - let them prioritize it and schedule it's fix. It can't be critical if it has been in production and not been noticed, but there is a chance that the fix may cause it's own problems: one coder I recall had an oscillating bug. When she fixed the one, it caused the other. When she fixed the second, it caused the first. Round and round we go...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Err no. If you change code, it must be tested.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
Good management hat! Document everything before and after the fact, that way you can see not just what changed by the reason why.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
The lesson to be taken out of this is what procedures do you need to put in place to prevent an occurrence like this happening again. If the bug is that big, it should be squeaky bottom time for your test team. They will be the ones who gave to explain why they never saw it.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
true - I had a small talk with them about it and they just raised the shoulders... oh boy!
regards Torsten When I'm not working
-
Good management hat! Document everything before and after the fact, that way you can see not just what changed by the reason why.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
Good point :thumbsup:
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
NO! Naughty boy! Unauthorised and unrecorded changes in production software? Ouch! Shove it up the food chain - let them prioritize it and schedule it's fix. It can't be critical if it has been in production and not been noticed, but there is a chance that the fix may cause it's own problems: one coder I recall had an oscillating bug. When she fixed the one, it caused the other. When she fixed the second, it caused the first. Round and round we go...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
NO! Naughty boy! Unauthorised and unrecorded changes in production software? Ouch! Shove it up the food chain - let them prioritize it and schedule it's fix. It can't be critical if it has been in production and not been noticed, but there is a chance that the fix may cause it's own problems: one coder I recall had an oscillating bug. When she fixed the one, it caused the other. When she fixed the second, it caused the first. Round and round we go...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
OriginalGriff wrote:
NO! Naughty boy!
Unauthorised and unrecorded changes in production software? Ouch!Whachewtorkinbout Willis? Earlier this week, new (2.5 weeks) ICT Manager of customer and ICT Operations Manager sit down and decide to make changes to the production Active Directory and Exchange. They decided to Disconnect all Mailboxes for accounts in the Disabled User OU. Problem is, someone (I reckon the same people) had disabled accounts that shouldn't have been disabled (1 of the 5 Board Members among others) and also moved accounts for Room Mailboxes (which are Disabled by design) into the same OU. So I had fun fixing the Elephant Ups and even more fun when during the moving of accounts to the correct OU's before Enabling them in AD and then Connecting them again in Exchange, I had the same knob-jockeys making furthers changes to the OU structure and connecting mailboxes without informing me and I was going mental trying to understand why I couldn't find acounts to connect too, even though I could see the accounts in AD. I deserve a large payrise as I have left all involved with all of their teeth.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
Holly s***! I found a mega huge bug this afternoon in one of our programs. The bug is there since at least half a year and nobody saw it or noticed it. Not us, not the test department, not the customers. But it's definitely there. Seems like I'll have to be the unlucky messenger to break the news. no good. absolutely no good. not good at all.
regards Torsten When I'm not working
-
OriginalGriff wrote:
NO! Naughty boy!
Unauthorised and unrecorded changes in production software? Ouch!Whachewtorkinbout Willis? Earlier this week, new (2.5 weeks) ICT Manager of customer and ICT Operations Manager sit down and decide to make changes to the production Active Directory and Exchange. They decided to Disconnect all Mailboxes for accounts in the Disabled User OU. Problem is, someone (I reckon the same people) had disabled accounts that shouldn't have been disabled (1 of the 5 Board Members among others) and also moved accounts for Room Mailboxes (which are Disabled by design) into the same OU. So I had fun fixing the Elephant Ups and even more fun when during the moving of accounts to the correct OU's before Enabling them in AD and then Connecting them again in Exchange, I had the same knob-jockeys making furthers changes to the OU structure and connecting mailboxes without informing me and I was going mental trying to understand why I couldn't find acounts to connect too, even though I could see the accounts in AD. I deserve a large payrise as I have left all involved with all of their teeth.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
But I bet you have left a lasting record of the changes somewhere! Either via profanity or bruising... :laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
