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!

  • sorrybookbroke@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    1
    ·
    1 year ago

    Yeah I don’t know man, as a dev this sounds like you are finding things that cannot be reproduced and the dev can only get more information from your machine. It’s like if you were calling up a mechanic on the phone. He can’t take the wheel. Would you be ok with giving them access to your PC remotely to try and find the bug?

    Nah man, we’re not trying to weasle you into finding the bug yourself. We would very much prefer to interact with end users as little as possible.