Ah, but testers don't break things--we merely find the places where they're already broken and point them out.
Sorry, knee-jerk there. I've been told too many times late in a product cycle that I am (or my team is) "finding too many bugs" and thus putting the product in danger of slipping.
To which my response is _always_, "Would you rather have the customer find them?" The bugs are there whether I find them or not.
Of course, at some point, the pressures of the market determine that, yes, it's time to let the customers find the bugs on their own. So I spend the last six months of the product cycle getting beat up at work for finding too many bugs, and the first six months after release getting castigated by the press and the customer for not finding enough of them. (Of course, half the bugs the customers encounter are bugs I've already found but which were not deemed important enough to fix.)
And all because people buy into the shorthand "testers break things".
Not that I am bitter. :)
That said, I'm frequently going to my boss and telling him about the latest thing I've "broken".
I just hate to see testers getting beat up unfairly for poor-quality software releases, so I have to take the opportunity to get my side of the story out there.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2006-06-30 03:41 pm (UTC)Sorry, knee-jerk there. I've been told too many times late in a product cycle that I am (or my team is) "finding too many bugs" and thus putting the product in danger of slipping.
To which my response is _always_, "Would you rather have the customer find them?" The bugs are there whether I find them or not.
Of course, at some point, the pressures of the market determine that, yes, it's time to let the customers find the bugs on their own. So I spend the last six months of the product cycle getting beat up at work for finding too many bugs, and the first six months after release getting castigated by the press and the customer for not finding enough of them. (Of course, half the bugs the customers encounter are bugs I've already found but which were not deemed important enough to fix.)
And all because people buy into the shorthand "testers break things".
Not that I am bitter. :)
That said, I'm frequently going to my boss and telling him about the latest thing I've "broken".
I just hate to see testers getting beat up unfairly for poor-quality software releases, so I have to take the opportunity to get my side of the story out there.