If mistakes happen, then the subject has not
been effectively communicated. No matter what opinion the communicator may have about their communication.
This is very frequently a problem for programmers and other technical types. The way I put it is that, Programmers tend to communicate precisely and ineffectively. Meaning that programmers tend to make sure that their communication says exactly what they mean, but then run into trouble because the person they are talking to is simply not ready for a precision where every nuance matters. Therefore, even though you've correctly said everything that needs to be said, you haven't actually communicated anything.
I think this happens because the mindset that you need to be in to do technical work is extremely precise, and it is hard to switch in/out of that mindset when talking to others, but very few people are normally in that kind of mindset.
However it doesn't really matter why it happens. What is important is to realize that it does happen, and to try to compensate for that. (A very common and useful method of compensating is to have a person between the technical person and the end user who is good at "translating".)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||