On Sat, Jan 31, 2009 at 3:29 PM, Thomas Hruska <[email protected]> wrote:
> BTW, stuff like this happens ALL the time. As a C/C++ developer, you
> WILL get yelled at when "it" breaks for not having thought of that "one
> something-or-other issue". It is important to quickly fix the problem
> (without panicking and introducing new problems in the process), take
> the yelling in stride, and add the issue to your test suite/alter how
> you do things so it doesn't resurface in the future.
>
> You will NEVER catch all issues because you see several trees instead of
> seeing the forest OR, if you see the forest, you will NEVER see each
> tree. Catch-22.
This kind of stuff is what keeps me employed... I work in tier3
support which means my team handles fixing bugs that come in from the
field (as opposed to bugs found during system test and QA processes,
for which our development team is responsible for handling
internally). We also issue patches to customers and assist our "tech
support" teams (the people who deal with the customers so the
engineers don't have to!) And believe me, we have gotten some silly
stuff come in that makes you scratch your head and think "How in the
world did this get past unit testing and system testing?" As we say...
excrement occurs.
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
