How to communicate effectively as a developer
Here is my competing take:<p>The biggest problem I see in developer communication is what I call the &quot;assumed context&quot; problem.<p>As in, you talk&#x2F;write to people as if they know all about your code, except the detail being discussed. In reality, they usually have much less detailed understanding, and you&#x27;re making no sense to them.<p>I&#x27;m pretty sure this is related to people &quot;on the spectrum&quot; often having low &quot;theory of mind&quot; capabilities. People without that will just assume people know what they know, and proceed to fail at communicating with those who don&#x27;t.<p>It also makes it easy to think of those who don&#x27;t know what is obvious to you as idiots.<p>The workaround, if you <i>want</i> to communicate with the idiots surrounding you, is to start conversations by fact finding. The question &quot;so how much do you know about the flurbigator system?&quot; can help.