Alex Zavatone writes:
If we spend the time to enter bugs that don't get fixed, it ends up being a waste of our time.
We have no control over if Apple choses to fix our bugs or not. Do we waste time working around a bug, then waste time reporting it?
I've got capitalization on an NSString failing at the moment with no change in
the string and have to write a method that works. If I have no faith that Apple
will fix my bug, then what is my justification to narrow down the bug and
report it when I will be staying late in the office as it is already? Taking
the time to report the bug if we don't know if it will be fixed doesn't help
our products ship any faster. Sad reality, but it's true.
In this neck of the woods, we call that a self-fulfilling prophecy. We don't have
"control" over whether Apple fixes bugs or not, but we do have influence. All work,
including bug fixes, is going to get prioritized in order to attempt to maximize the effective use
of finite resources. We influence that prioritization by filing bugs. If you believe your bug is
such an edge case that only one person in a decade runs across it, then you're probably right: It
won't get fixed because it won't bubble up in the queue high enough to displace more impactful
tasks. On the other hand, if 100 people a year are running into a bug and only 1 of them reports it
because everyone else "knows" it will be a waste of time...well, the other 99/year have
no one to blame but themselves.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
