In Orr's ethnography of photocopier repair techs (https://www.goodreads.com/book/show/20081966-talking-about-machines), he discusses how techs have to educate copier users to produce good bug reports - that is, descriptions of problems useful to the techs in diagnosing the underlying problem.

I'm way out of date in software testing. Back in the day, software testers educated each other about writing good bug reports, and about how to escalate a minor bug into one that people feel compelled to fix. (I remember this being called "failure amplification", perhaps coined by Cem Kaner? Bret Pettichord? It was a skill associated with the best testers.)

And open source projects often have descriptions of how to write a useful bug report. In my experience, those are mostly written by programmers and directed to other programmers.

I'm not aware of examples of programmers in an organization specifically thinking part of the job of fixing a bug is to make the tester better at reporting bugs. Have I just been missing it?

I pay $5 a month for the comment service below (rarely used), but it'd be better to continue this conversation on Mastodon.