Soft skills or how not to be bad and beech

Hello, my name is Dima and I’m a developer at Turbomates Soft. In this short article, I want to talk about a rather hackneyed, but no less important topic like soft skills. I will consider the relationship in the team more from the side of the IT sphere, but the conclusion is applicable to any profession.

Today you can often hear the word `toxic`. It seems to me that this word was invented by evil people to call names of the same evil people, so let’s replace it with a more Orthodox one – for example, beech. It would seem that it could be easier not to be those bad and beech? Unfortunately, it is not so easy to understand that you are a real beech.

We can quite easily describe the standard development path of a programmer. When from a coder performing tasks, we turn into an excellent programmer who finds a common language not only with the team, but with the business. When we not only look for answers to questions, but also ask them. As this development progresses, we will have to communicate more and more and the result of our work will depend more and more on how well we hear and listen. Based on this, I want to highlight some markers that, in my opinion, will help you be heard and make a good impression of you in any working and non-working environment.

1. You can be wrong

All people can make mistakes. But for some it’s easy to admit it, but for some it’s the end of the world. In fact, we are afraid not to make a mistake, but we are afraid of the reaction to our mistakes. In childhood, many were afraid of getting a bad grade because they were afraid of the reaction of parents and teachers to our misconduct. Therefore, you need to learn how to correctly tell a person what can be done better. Learn to defend your point of view without diminishing the importance of the other’s point of view.

Useful phrases: [по моему мнению; как мне кажется; на мой взгляд]

2. Share your experience, don’t store it

Share your experience with others if you are asked of course. `Experience` as a word has absolutely no weight, but the history of this experience can be a good justification for your point of view. Many experienced developers don’t want to bother with explanations, because it’s much easier to say just do it. But there is also a reverse situation, an unreasonable dispute on the part of less experienced colleagues. If you are not constructively defending your point of view, then most likely you are a beech.

Harmful phrases: [тебе еще учиться и учиться; потому что я так сказал; ты бы лучше послушал, чем спорить; мы с тобой на разных уровнях, сколько раз я буду повторять …]

3. Do not create unnecessary hierarchies

I like to imagine that my development team is a football team. We can have a captain, we can get different salaries. But on the field, we are all equal players on the same team, in the same shirts and with the same goal. It happens that, using authority, we create an internal hierarchy in the team, thereby making it difficult to communicate and transfer experience from senior to junior. I am generally not a supporter of strict hierarchies in the company and in the team byak and beech, it seems to me that it looks like this:


4. Respect the work of others

5. Patience is the weapon of the weakest and the strongest

Such points may seem to someone naive and not related to the real world. However, in my opinion, these rules are simple to disgrace, like etiquette or a good tone of communication. The conclusion from all this is quite simple. If you want to be respected, respect others. If you want to be heard, listen to others.

What else can be added: put your fingers up, click on the bells and write comments!

Dima jin_enjine

Software Engineer | Turbomates Soft

Similar Posts

Leave a Reply