As a popular industry group nowadays, programmers not only have stable jobs and considerable salary, but also attract more and more small partners to join the programmer team.
Due to the special nature of work, programmers' daily social circle is not extensive, so that they are not familiar with the way of doing things in the workplace, especially if some sensitive topics are not paid attention to, it is difficult to avoid frustration in the process of workplace communication and job promotion.
Today, Huizhimei is here to take stock of the "8 Taboos in the Workplace of Programmers" for everyone , and I took a small book to write down:
1. A small achievement that stops in front of you
Some programmers start from a relatively high starting point and have excellent IT skills, so they start to be complacent, which is undesirable.
It is important to know that IT industry technology is updated and iteratively fast. Existing skills can meet temporary work requirements. Occasionally encounter difficulties, there may be guidance from seniors, but if you want to have more "prestige" and competitiveness in the department, you need to continue Maintain a learning attitude and always arm yourself with new knowledge and skills.
Otherwise, you will not only encounter the embarrassment of older programmers in the workplace, but also face the potential risk of being eliminated by newcomers in the workplace!
2. Despicable, arrogant and domineering
To tell the truth, as long as the small partners engaged in technology, there will be more or less conceited, so that no one speaks and does things, which in turn causes emotional contagion in the workplace.
For newcomers in the workplace, old people are originally needed to bring help, but in this process, it is inevitable that a situation of sturdy attitude and malicious attack on newcomers will occur, so that the originally active newcomers are burdened with a lot of pressure, which affects the overall department. Work process.
There is another situation. They like to point out and recommend various learning promotion materials in the face of inferior skills and unreasonable design. In the long run, it will inevitably make the other party feel looked down upon, which will trigger a workplace and office storm.
It seems that a smart heart is also quite necessary. How to control this degree is really a compulsory course that needs to be studied well.
3. Get involved in workplace disputes at will
There is a kind of person in the workplace who likes rampage, disregarding the company's rules and regulations, and acting style often likes to get involved in other disputes, and even wanton cross-level reporting...
The details determine success or failure. The Xiaomi server mentioned in the previous article was hacked, and the problem was also caused by the random mapping of the internal network port to the external network, and was eventually transferred to justice for violating the company's rules and regulations.
It is said that there is no rule to make a circle. In the workplace, you need to remember: be low-key, humble, and find your place.
Isn’t there such a sentence? The best life advice is not to give life advice to others; the best way to communicate is to learn to shut up.
4. Easily agree to others' requests
Although the workplace is not as good as the battlefield, it must be good at feeling the warmth of people's hearts. Some programmers like to be good old people. Over time, a colleague will come and call you to help solve a problem. Tomorrow, you will be responsible for the mess, and you will pat your ass and leave to be the shopkeeper.
In fact, it is best to stop this situation in time when it shows signs. It is necessary to know that rejection is not an unspeakable thing. There is no need to please or tolerate it because of face or considering the other party's feelings.
The kind of pain experienced by good people in the workplace, I think if he is given another chance to choose, he will definitely not want to experience it again.
5. Speak ill of colleagues privately
Programmers often deal with code and data, the way of thinking about problems is inevitably "straight", and they are more inclined to treat department colleagues differently based on their technical ability.
When the company evaluates its employees, it is unavoidable that the good and bad things will be heard in private, which will inevitably be heard by the parties, which will affect the feelings of colleagues and follow-up work cooperation.
6. Self-sealing
This scenario may be more suitable for management posts. From the front-line technicians to the management posts, they begin to lead the team, grasp the project, and prepare to implement their grand plans. They do not know that they are about to face various unknown challenges.
For the elderly in the workplace who have adapted to their current working conditions, they are often those with high resistance when facing adjustments and changes. Therefore, forced drastic changes at this time will inevitably bring negative emotions to the group, resulting in a large blow, and even difficult to advance. Therefore, it may be an effective way to promote the development of matters step by step.
7. Share resignation ideas with colleagues
In fact, this can be regarded as a kind of emotional contagion. The reason why I bring it out separately and re-emphasize it again is that after Huizhimei has a lot of programmers around me, after the idea of leaving (or quitting), he spread all kinds of dissatisfaction to the company colleagues. Continued internal fermentation, eventually resulting in very bad consequences.
This not only makes existing colleagues unable to settle down in their own work, but also affects the stability of their new job (during the on-boarding return visit, the personnel department of the new company will contact the former company for return visits to gain a more objective understanding of the work style of employees. ).
8. Take credit and arrogantly evade responsibility
It is a common situation in the workplace that what I know is hesitant to share with my colleagues, fearing that it will affect the competitiveness of the workplace, and being learned by my colleagues to surpass myself.
In fact, it’s not necessary. Learning to share will not only gain the recognition of colleagues and enhance work emotions, but also discover problems that I did not have previously aware of, so as to improve, open the door to a new world, and learn more knowledge and skills.
In particular, the phenomenon of arrogance and madness encountered in the workplace is also due to the fact that they do not share, they are self-contained, and they are isolated and closed. Just ask, without the embodiment of the sense of collective honor, how can the behavior of detaching from the departmental collective can stimulate the collective vitality?
The above are some taboos that programmers need to pay attention to daily in the workplace. It is said that the small partners who can achieve more than 80% may be destined IT elites!
Although IT people often deal with code and computers, they also need to understand that programmers are also flesh-and-blood, emotional and social needs. Putting aside the daily relationship between workplace and colleagues, for individuals, more exercise in EQ is also beneficial to daily life. In the world.
Especially for the small partners who are troubled by leaving the order, they need to strengthen their soft power in this area. Otherwise, one day when you meet your favorite Ta, how can you not seize the opportunity?