in reply to What Kind Of Programmer Are You?
I think it's always best to probably look at the code,
before you deny anything that there may or may not be a
problem (even if it could have been user error). It's easy
enough to see if it was the code. If it was, fix it asap - and
if it's not.. show the user or whoever spotted the problem how
to use the program or see how they used it to create the
error. To have an attitude about one's code can be alright,
but often not just causes a problem in communication down
the road.
In Section
Meditations