News for hackers. Stuff that matters.

nhgrif

Re:Does Not Work on Friday February 03, 2017 @08:20AM (#13559582)
How do we know whether or not we're properly reproducing whatever they're seeing if we don't know what we're seeing?

I've seen scenarios where a set of reproduction steps actually showed two things wrong. QA was sending it back for one of the things, but they didn't say what was wrong, only that something was wrong and here's how to reproduce it. The developer saw the other problem, and fixed it. The result when shipped back to QA?

"You didn't fix the problem, but I opened a new defect now for the other thing you broke."

Re:Does Not Work on Friday February 03, 2017 @08:17AM (#13559572)
Hey people, author here.

I've seen a lot of comments about the tone of the article or how this isn't the best approach to take with someone who literally exhibits this behavior. And if you take the post literally and from the point of view of the person being asked advice, you're pretty much right (unless of course we're talking about this strategy as a literal response to Stack Overflow posts).

In truth, this is not my literal approach when people come to me exhibiting this behavior. I'm actually quite a lot nicer in person (believe it or not). Really, this article was written with the hope in mind that it would be read and shared with people who aren't particularly good at exploring the WHY of "does not work". In fact, almost all of my articles are geared toward entry level developers.

Anyway, I'm glad most of you seemed to enjoy it, and pretty much all of you agreed that the overall sentiment of the post is good advice, even if you didn't like the tone (which is perfectly fair).