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....
Of course… The reaction shows how seriously wound tight people are. Obviously not much sense of humor in this community.
There are a couple rare cases where devs have tried to coerce me into a fix. Sometimes they outright say they expect the bug reporter to fix it, strangely enough. It never happened in a language that I knew, and weird that bug reporters would be expected to know how to program at all. But it’s far from the norm.
Someone tasking someone else without paying them is indeed being not where they belong. In the case of the OP, that’s the dev tasking the bug reporter.
That’s fair enough, but it’s a bit of both (satire and reality). It’s actually a true account (details withheld because I have a bit of respect for the developer in the recent case). This is something that really happens. Not often, but occasionally there are devs & others who expect bug reporters to do a fix. There’s a poor attitude that bug reporters are in some way a beneficiary/consumer and the false idea that the devs are working for the bug reporter. There’s also an assumption that the bug reporter is in some way in need of a fix. When in fact the bug reporter is a volunteer contributor, performing work for the project just like the dev. It’s just as wrong for a dev to demand work a bug reporter work on the code as it is for a bug reporter to demand work from a dev. Everyone gives what they can or wants to. A bug report is not an individual support request. It’s a community bug – one that may or may not even affect the bug reporter.
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.
much larger contributions of the developers.
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.
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.
I wondered what that article would say about Ada. No mention. But certainly Ada gives you the ability to have the issues that are listed so apparently Ada is memory unsafe (despite it being highly regarded as a safe language overall).
Also worth noting that Ada developers generally consider rust a watered down lesser alternative. OTOH, rust has memory safety and Ada does not, correct?
Watch out for devs trying trick bug reporters into doing work
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....
What is memory safety ( alexgaynor.net )
this article brought me back to www.pl-enthusiast.net/2014/07/21/memory-safety/