Sometimes I report a bug & the dev starts off asking for more details. But then there’s a kind of scope of effort creep where you start to realize you’re being tricked into finding where in the code the problem is so you can fix the bug.
It’s a bit of social engineering of sorts. When I post a bug, I do that from the back seat of the car. And it’s like the dev sits in the backseat as well while coercing me into the front seat. So sometimes there’s a bit of weasel words and nuances with sneaky wording that needs to be deployed in order to stay in the backseat while trying to get the dev into the front seat where they belong!
And? Of course testers do not pay money. Why would they? Devs do not pay for the tester’s work either. Both developers and testers are volunteers who do not pay the other for their work. On free software projects testers and devs pay with their own labor.
It is not “much larger” for a dev to task the tester to implement the fix. The dev is no more than a manager in this case.
Programming contributions >> incomplete bug reports
Did I say incomplete? You’ll have to quote where you get that from.
Compare like with like. You can have incomplete code, and you can have incomplete bug reports. Neither are relevant here.
This whole post is you defending a half assed bug report.
What bug report? There’s no bug single report in particular to speak of. I’ve filed hundreds if not thousands of bug reports over the years. The post is a reflection of a subset of those experiences.
When a developer asks a tester to look at a module in the source code, that is not a consequence of a “half assed bug report”. It’s the contrary. When a dev knows a particular module of code is suspect, the bug report served well in giving a detailed idea of what the issue is.