Skip to content

Software Engineer's Communication

Hoseock Choi edited this page Feb 25, 2020 · 3 revisions

General

Why Communication?

Do you need me to explain why communication skill is important to the Engineer? well if you are a Software engineer, some of you may think you work alone. Just completing the task is the one big thing that is important. However, what you can do alone is very small that in the long run, you will need to communicate with others to understand the requirement, objective, possibility, risk and so on.

Although It is fundamental to do any kind of working activity in the organization, we barely learn and practice effective communications.

Here we want to talk about why communication skill is something that we need to understand and how we can practice to improve it.

Don't worry if you think you are not clever to learn something difficult, because you only need GRIT to learn it. Nothing more than that.

Pair programming & Code Review and...

When it comes to the activity of software engineer, pair programming and code review is one of the hot topics. People say that, with the code review, they can find the potential defect which can reduce the cost of software product sustainability and improve the quality of it.

And if we do pair programming, we can write the code and review it at the same time(??). How good it is!!

Well, it's half true and half wrong, you may do these two at the same time, but in order to have a pair, you need at least two people.

But, when you are in a situation where two modules are meeting each other, in other words, implementing the interface or boundary of the module, it is certainly a very effective technique to use.

And not only in a situation like above, but it's also good for the people who joined recently. Imagine, that you joined this team yesterday but received a task to implement. If you are alone, you need to study the code which you think directly related to the feature that you need to implement and write the code in a very narrow view on the problem. However, if you have a pair to work together, you can act as a driver and he acts as a navigator to tell you from the broad perspective with the knowledge and the experience related to that feature.

I can not say, pair coding is the ultimate weapon that can be used to solve all the problems, but if you use this technique in the right situation, I am sure you can improve the productivity of your team.

"Important but not urgent" rule

Consensus in team

Ground rule

Communication technique

Get to the point

How to say it

Your body Speaks

Building a trusting team

Confession

Growth mindset

Developing a Growth Mindset with Carol Dweck

Cognitive learning theory

then Why Communication again

  • Because it's the one most important thing that lasts in the end.

References

  • GRIT
  • Role of Technical Leader
Clone this wiki locally