I knew that people thought I had bad social skills, but they weren’t able to explain the situation to me in a way that I could understand, because they were totally misinterpreting me, on account of not knowing what was going on in my mind.
A useful analogy is bug reports made by non-programmer users. They are sometimes right that there is a problem, but most attempts on their part to formulate what it is or “${deity-}” forbid what is the cause is so confused that saying nothing is an improvement. You have to reproduce and debug the problem yourself. Another example is writing: “the reader is always right” in the sense that unexpected negative reaction is a flaw in your model of the reader’s perception of your work, even if the reader is wrong about the reasons for their reaction.
Each clue about an error is a poorly or misleadingly stated bug report, and there is usually nobody qualified to investigate the issue if you don’t do it yourself, of your own initiative: formulating hypotheses, running tests, observing responses.
A useful analogy is bug reports made by non-programmer users. They are sometimes right that there is a problem, but most attempts on their part to formulate what it is or “${deity-}” forbid what is the cause is so confused that saying nothing is an improvement. You have to reproduce and debug the problem yourself. Another example is writing: “the reader is always right” in the sense that unexpected negative reaction is a flaw in your model of the reader’s perception of your work, even if the reader is wrong about the reasons for their reaction.
Each clue about an error is a poorly or misleadingly stated bug report, and there is usually nobody qualified to investigate the issue if you don’t do it yourself, of your own initiative: formulating hypotheses, running tests, observing responses.