Re:The Better You Program, The Worse You Communicate
by JacobAldridge on Monday June 08, 2009 @08:21PM
(#648287)
I think this is particularly relevant for verbal communication, and less so for written communication (where, as an example, you can employ DRY as a confused reader can go back and re-read what you wrote).
Some of the key components of programming, however, are also key to good communication. Make a point, and progress directly to that point rather than waffling around. If a term is ambiguous, discuss possible definitions and agree on one (or use a different term).
What about Write/Communicate, Test, Iterate. Say or write something; ask or check if it was understood (eg, by having the person repeat it back to you); if what you get back isn't what you meant to communicate, communicate again.
And finally, take responsibility for your communication as you would for your code. Don't blame the listener any more than you would blame the program or language. If you wish to be understood, seek first to understand the other person's communication needs.
Some of the key components of programming, however, are also key to good communication. Make a point, and progress directly to that point rather than waffling around. If a term is ambiguous, discuss possible definitions and agree on one (or use a different term).
What about Write/Communicate, Test, Iterate. Say or write something; ask or check if it was understood (eg, by having the person repeat it back to you); if what you get back isn't what you meant to communicate, communicate again.
And finally, take responsibility for your communication as you would for your code. Don't blame the listener any more than you would blame the program or language. If you wish to be understood, seek first to understand the other person's communication needs.