I agree: to quote Einstein: "If you can't explain something to a six year-old, you don't understand it yourself". Even though most of us (here) are reasonably technically proficient, I think (huge generalization coming up) that even we find it easier to understand things that are written in a natural language - after all, natural language is the tool we use every day.

One of the arts of communication is tailoring your output to the audiences' level of comprehension - if you're talking to your non-programmer manager, you'd hopefully use language that he/she could understand. Trying to "blind with science" tends to make you appear arrogant, and will often alienate your audience. If that audience has some influence on your wage-packet, I'd watch out.
As programmers, we generally have a higher level of technical knowledge than the average (customer, user, individual), but giving descriptions in "user-language" actively helps your ability to communicate.
My 2 cents, take with the appropriate quantity of sodium chloride.

davis
Is this going out live?
No, Homer, very few cartoons are broadcast live - it's a terrible strain on the animator's wrist

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.