Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualHaps

Posted 03 October 2012 - 01:11 PM

Flowcharts, diagrams, and mockup pictures can often provide better detail than words can.

If you're trying to communicate the general flow of a smaller idea, sometimes pseudo-code written in structured English can help - if you know how. Don't just start using it on the spot, because it takes a bit of understanding of the structure of a programming language, and knowing what we need to hear.

Overall, as the others have pointed out, speaking plainly is best, then you're likely using a language both of you have been proficient in for years. For technical terms, be absolutely sure of them: If the word doesn't mean what you think it does, you're going to get pretty far apart on the end result. Don't try to "reach out" and use a word you've heard two or three times, thinking it's what we want to hear.

(You know this isn't targeted at you specifically, just speaking in general about the problems we've all run into!)

#1Haps

Posted 03 October 2012 - 01:09 PM

Flowcharts, diagrams, and mockup pictures can often provide better detail than words can.

If you're trying to communicate the general flow of a smaller idea, sometimes pseudo-code written in structured English can help - if you know how. Don't just start using it on the spot, because it takes a bit of understanding of the structure of a programming language, and knowing what we need to hear.

Overall, as the others have pointed out, speaking plainly is best, then you're likely using a language both of you have been proficient in for years. For technical terms, be absolutely sure of them: If the word doesn't mean what you think it does, you're going to get pretty far apart on the end result. Don't try to "reach out" and use a word you've heard two or three times, thinking it's what we want to hear.

PARTNERS