Talking to Developers

Today's takeaways

- It has gotten to the point where: 결국 ~하게 되다

보통 negative한 맥락에서 많이 쓰인다고 함

e.g. It has gotten to the point where he has not cleaned his room in 10 days.

- urgent = time-sensitive

- No matter what vs. whether or not vs. Regardless

 

• No matter what = you are going to do it regardless of obstacles = EX: I am going to arrive to work early no matter what.
• whether or not = in any case = EX: Whether he wants to or not, he'll have to clean his room.
• Regardless = anyway, despite the circumstances = EX: This job is open to all, regardless of previous experience.

 

Q. Are you a developer? If so, do you ever struggle to communicate with different team members? If not, do you ever struggle to communicate with developers? Explain.

I’m not a developer. As a technical writer working at an IT company, I sometimes struggle to communicate with developers. Developers are usually very busy; they seem to struggle with developing new features and trying to fix bugs under time constraints. But, I need their help when trying to understand technical documents or technical concepts. Due to the fact that the developers have created these programs, they can best explain their process.

 

So, I do research before talking to developers to have a better understanding of their products. For example, I go through all the available resources, such as user guides or webinar YouTube videos explaining the company products. Additionally, when I am unable to get in touch with the developers, I reach out to colleagues who have technical knowledge that can guide me like engineers. In this way, I tried to figure out some unclear parts of the products and then did a final check with the developers.

 

Q. What do you think is most important when it comes to communicating across teams?

The most important thing in communicating across teams is to provide the outline before meetings. It’s necessary to tell the purpose of communication and document it. In order for a meeting to run smoothly, meeting hosts should organize tasks and provide the goal for the meeting. I suggest that people should discuss the agenda at the start of the meeting. 

 

Q. Do you think different interests across teams is the main reason for communication difficulties? If not, what do you think is the main cause for struggles in communication?

Yes, I think different interests across teams are one of the main reasons for communication difficulties. Regardless of whether or not they have a purpose, each team prioritizes their most urgent task. As a result, even if some work is important to me, it could be pushed back on the priority list of other teams. It has gotten to the point where different groups argue about priorities and the urgency of tasks.

 

Another reason for communication struggles is the lack of thoughtfulness and empathy. Some people are more direct and do not consider other teams' emotions when having to say no. Even if they didn't do it on purpose, people must be more cautious when dealing with rejection.

- Even when people are delivering the same message, taking a direct approach can cause a team member to feel slighted.
- Some team leaders lack consideration for their team members' emotions and are abrasive.

slight = insult (someone) by treating or speaking of them without proper respect or attention.
abrasive = (of a person or manner) showing little concern for the feelings of others; harsh.

 

Q. What mindsets are necessary to enable effective communication between developers and non-developers?

Developers and non-developers need to have the mindset that we work as one team. I know that every colleague puts in a lot of effort in order to achieve results, but collaborating and communicating will allow for better overall performance. Some people are narrow-minded, saying that only their work is essential. They don't care about others, but at a company, each team is linked to one another. If teams collaborate effectively, they can grow together.