Programmers don't want to be monks

nonsenseMonk Sha is a model of honest and honest work. He is hardworking and bears the burden of death embarrassment.

Most of the computer software developers have the shadow of monk Sha. Basically, they only know how to work hard. After finishing the work, the leader does not know that you are busy, because the leader does not see that you are busy, or even hear that you are busy, so naturally you are still busy. your own. And some other people, if they do a little thing, will go to the leader to say it, and let the leader know. On the one hand, they have more contact with the leader, and on the other hand, they let the leader know that they are doing things, so it is natural to be valued and benefited.

One of my best friends is a monk-like figure. He works in a business unit. He doesn't like or is not used to contact with leaders, so he has been attacked. His computer level is very high, he has passed the department points, and has a strong ability to develop projects. However, when his unit has money in the development project, he is not allowed to develop it, because it has been robbed by others. However, for such a high-level person, the leader arranged for him to do operational support, that is, to work the night shift at night to do some mechanized operations, to answer the phone during the day, to deal with problems, and to plug the butt of the developers. There are no holidays or breaks at all. This kind of work, their unit has two systems analysts for this work, but the development department does not have one! A leader even said to him that leadership in a state-run unit is the same power that hangs you up! However, the hanging here is the hardest part of the distribution. There is no credit for the operation and maintenance work. It should be done well, and it should be punished if it is not done well.

so poor. Destiny is in your own hands. Never be a sand monk! Human abilities should have a place to play! So, how can you not be a monk sand? Pay attention to one point, more than leadership communication, specifically, often reporting work to the leadership:

Reporting work is to report to the leader what he has done, what he is working on, and what he will work on, so that the leader knows what to do. Don't do it when you're done, don't make a squeak.

Some people may think that a matter is handed over to you, and you can just tell the leader after you finish it, and there is no need to report in the middle. In fact, this kind of thinking is also wrong. If one of the leaders attaches great importance to this matter, they must hope to grasp the progress, and the progress needs to be reported by you halfway. Second, can you guarantee that you can complete the whole thing satisfactorily? There may be many ways to complete an event. Can you know which one you choose is the most correct or the one that best suits the leader's mind? Third, you may encounter a lot of trouble in the process of doing things. Are you ready to carry it alone? When reporting midway, you can explain the progress and hand over the choice to the leader. At the same time, when you report, it means that things are done according to the leader’s wishes. When the sky falls, the leader will carry it, and of course the benefits will also be carried by the leader (this is inevitable). , not relevant for reporting).

Timely reporting is also a way to show respect to the leader, and to contact more leaders in the way of work, the relationship between the two sides will be closer over time, so that you will no longer be afraid and will naturally not hang up.

Sha monks, are you ready to transform?

(Note, the above article is written for monks, not suitable for Monkey Kings and Zhu Bajie)

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=327104072&siteId=291194637