Importance of communication and how to improve it

  • Thread starter Thread starter Grelbr42
  • Start date Start date
  • Tags Tags
    Communication
Click For Summary

Discussion Overview

The discussion revolves around improving communication in technical contexts, particularly in the exchange of information regarding data analysis and coding practices. Participants explore how to effectively ask questions to elicit clear and informative responses, especially when dealing with complex scripts and methodologies.

Discussion Character

  • Exploratory
  • Technical explanation
  • Conceptual clarification
  • Debate/contested

Main Points Raised

  • One participant recounts a challenging interaction where they struggled to obtain clear information about the uncertainties in a coworker's analysis, emphasizing the need for better questioning techniques.
  • Another participant suggests that it is natural to have iterations in questioning during initial interactions to clarify complex topics.
  • Concerns are raised about the lack of comments in the code, which may hinder understanding and communication about the implemented algorithms.
  • Suggestions are made to ask specific questions about the algorithm or to request visual representations, such as flow charts, to facilitate clearer communication.
  • A participant notes the absence of comments in the code and mentions the use of unclear variable names, which complicates understanding.
  • One suggestion for improved questioning includes asking about the underlying methodology used for calculations.

Areas of Agreement / Disagreement

Participants generally agree on the importance of clear communication and the need for better questioning strategies, but there are differing opinions on the best approaches to achieve this clarity.

Contextual Notes

Limitations include the potential for misinterpretation of questions and the reliance on the clarity of code documentation, which was noted to be lacking in this instance.

Who May Find This Useful

Individuals involved in technical communication, data analysis, or programming, particularly in collaborative environments where clear understanding is crucial.

Grelbr42
Messages
69
Reaction score
125
So the generic question here is, how to improve communication?

Recently I started a review task for a coworker's analysis. One of the items in the report for the analysis is a graph with a linear fit of some data. And the linear fit has uncertainty reported in the fitting parameters. So I ask "What did you do to produce these uncertainties?" His response is "I calculated them." Um... Click click click. "Yes, but what did you *do*?" So he starts to show me his PERL script. "Wait. OK. What does the PERL script do?" He tries to show me more script. "No no. Source code is not documentation." He looks quite upset with me but pauses. "What does the script do to calculate the uncertainties?" Suddenly he's back in the groove, walking me through 200 lines of PERL. And suddenly I see that he has included a covariance matrix. Sigh. I know what the client will do with *that*. They have a very large pile of such things behind their facility. On the far side of the parking lot behind the trees. "So you used the textbook formulas, fed the data in, and got reports of the uncertainty of the fitting parameters, yes?" Well... Yes. But my PERL script... "No no, that's quite alright. I have what I needed."

How could I have asked this question so that my meaning got through?
 
Physics news on Phys.org
If this is the first interaction of this sort, then I think it is natural to have some iteration on questions to get to the heart of the matter. I suppose in this instance you could have asked what type of uncertainty or equations are implemented by the code. You kept asking what he did, and he definitely wrote code. You also asked what does the script do. These are all easily interpreted to require answer that talk about the script.
 
Grelbr42 said:
"No no. Source code is not documentation."
Was the code commented? Was there a good summary of the code in the comments at the top of the file?
 
Grelbr42 said:
How could I have asked this question so that my meaning got through?
Be careful. You could find yourself with the added responsibility of supervising this person. Extra work, much frustration, and at the same pay.

Some suggestions:

What is the algorithm implemented in your code?

Sketch the flow chart of the your code.

Sketch the flow chart of the algorithm in your code. Yes. Now. Freehand.
 
  • Like
Likes   Reactions: berkeman
berkeman said:
Was the code commented? Was there a good summary of the code in the comments at the top of the file?
No comments whatever. Variable names like xj and yq.
 
  • Wow
Likes   Reactions: berkeman
How could I have asked this question so that my meaning got through?

"What underlying methodology did you use to base your calculations on?"
 
  • Like
Likes   Reactions: Hornbein

Similar threads

  • · Replies 2 ·
Replies
2
Views
1K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 30 ·
2
Replies
30
Views
4K
  • · Replies 5 ·
Replies
5
Views
2K
  • · Replies 2 ·
Replies
2
Views
1K
  • · Replies 6 ·
Replies
6
Views
4K
  • · Replies 11 ·
Replies
11
Views
5K
  • · Replies 1 ·
Replies
1
Views
2K