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!
I actually agree.
I’ve filed bugs before with all the relevant details then after a huge conversation I’m told to write the fix.
In the situation I’m thinking of, I was asked to write a fix in a huge Python codebase as well as specs, JavaScript for the frontend, etc.
Bro, I’m a Rails developer. I’m not doing all that; I’m a user, not part of your organization. 🙄