Re: Array index nt valid

Hi Scott,

> Since I've already paid for the software,
> management doesn't usually think
> it's acceptable to throw it away and buy
> something else.  They seem to think that
> if I can work around the problem, I should.

No, they probably don't expect you to throw it away, and I didn't
advise that action.  Although I certainly _wish_ such an option
existed!  Yes, often management want us to work around vendor
problems, but it doesn't hurt to let management know that documented
problems exist.

> ...how do you convince the software
> manufacturer to put "Warning! My
> code sucks!" in their product literature?

You don't, but word gets around.  I currently work for a software
vendor, and references are our life's blood.  Customer satisfaction is
very high on our list of things to do today and every day.

> If I go to a software vendor and tell them
> that I've encountered an error, the first
> thing they do is talk to me like a 2 year old.
> After maybe a day of going back & forth
> with their tech support, they'll tell me how to
> write my program so that I won't get the error.
> They sure as hell won't put "It's my fault"
> in writing so that I can give it to my management.

As far as documenting known faults like an array index error under the
circumstances when a particular file is empty, I'd bet you could get
that one in writing.  Maybe not all bugs, but program messages are
particularly egregious.

> If they do, what will my management say?
> They'll tell me to work around the problem.
> Do you seriously think my management
> understands that they shouldn't produce
> this error?  Especially if the vendor has
> provided me with specific instructions to
> solve the problem by changing my own
> program?

It has been argued by several on this list that I don't seriously
think about anything!  :-)  Joking aside, I am forced to concur that
most management seem to have passed a Dilbert Pointy Haired Boss exam
as a prerequisite to their promotion.  Will the boss ask that you
'play nice' with Mr Software Vendor?  Most probably.  I believe that
it doesn't hurt to have a written record of the quantity and nature of
the bugs you are forced to deal with.  It's sometimes - just
sometimes - possible to convince the boss that something is awry when
he catches you updating the 'weekly bug count' spreadsheet.  He won't
want to be clubbed over the head daily with it, but a monthly status
might not hurt...  (I did say 'might'.)

  --buck