sixate, often the question is posed "who wrote the code" where the screw up occured. I probably didn't make that clear. The question is often an obvious attempt by higher-ups to find out which programmer is to "blame" for the mistake.
Often there's no way to test for things that may happen once the app hits the customer's particular environment, new data, etc.
When I say "I should have caught it". The person who is doing the questioning knows full well I am stonewalling and that I might as well be saying "I'm not about to give you leverage into my team operations. I'm taking the hit and I will deal with the error."
It's a sort of code that people understand. Believe me.
It's hard to explain but I think you can get the sense of what I'm saying.
__________________
create evolution
|