3 ms·
I revered my testers in those days. When they found a problem, I had to ask myself: "How did I miss this?". I'd identify how that happened, and made a note as
by GeorgeTirebiter 5y ago
I revered my testers in those days. When they found a problem, I had to ask myself: "How did I miss this?". I'd identify how that happened, and made a note as to how to eliminate that class of error in the future. It is a mistake, I claim, to not have professional FW/SW testers anymore. I fail to see how having a parallel set of professional testers adds delay to product release -- except insofar that the testers find bugs that end users will subsequently never see - and that's the point!
- scotty79 5y agoMe too. That was pretty much the only condition when I was looking for a job. Who does the testing? If the answer was "developer", or "everyone" I knew that they don't have a person who's responsibility is testing and that was very bad sign because I knew second pair of eyes responsible for looking at your output is worth their weight in gold. Being a great tester requires very different set of skills than being great developer.
- hinkley 5y agoThe over-under on good testers versus bad ones is at least a factor of three wider than good versus bad developers. I think a lot of backlash on QA is based on worst case scenarios. At a company that didn’t have remote workers, we let one QA person work remotely because she was that good at her job. She was finding more bugs than the next two people combined, and we had three people we considered to be “good”.