Will the boss thank you for writing code?

Program Members are keen to work for a long time. What I want to say is, just admit it. Your job/boss didn't let you do this. You just want to do it yourself. Of course, I know that not all programmers may like programming for a long time. But surely, with overtime becoming a common phenomenon in the industry, at least half of programmers must like overtime, isn't it?

I have heard of the following excuses. "No, it's not like that. We just like cool technical activities and don't want to leave unsolved problems. In fact, working overtime is a good thing. It makes us Outstanding !"

In my opinion, you cannot only see trees, not forests. From a certain perspective, you do not do this for yourself, but for "someone ". There is no need to question. He may be a noble man, but you are not his slaves. From other perspectives, how many times have you worked overtime to solve problems, research new technologies, code implementation, and complete tasks before the deadline? However, you are a witty developer in your business, and you are helping your company succeed. Company managers have already explained to you the company's economic situation-you must do so and the company depends on you. What I want to say is that this manager will not be worth anything unless it is now with you and chatting with you at midnight.

Let me tell a story that a friend once told me. This story is about a talented programmer. Just call him John.

John is a super star among millions of programmers. He understands and writesCodeSuperior capabilities, and 20 times the efficiency of anyone else. One day, the company got a short schedule. The customer provides a specification that frustrated everyone. John helped. He took the instruction book home, and no one had heard of him in the next three days. When he came back to work, he looked very embarrassed, but he understood the entire manual and completed the basic framework of the project. In addition to a small part of the statement that cannot be completed, John has completed the rest of the statement, even the customer does not know much about the requirements. It's amazing!

When I first heard of this story, I felt quite deeply. I asked the first question, "Where is John now ?" My friend replied, "he is dead, and his life is too difficult !" It may be more appropriate to use programming skills. Surprisingly, John is only 30 years old.

Programmers get extraordinary happiness by sharing stories about the death contest. Even when we do this with disgust, this dislike also carries a bit of pride to encourage our colleagues to do "better ". But it's a bit like the guys in shorts. Their shorts are as short as you can see their underpants. It's also a bit like some people who take smoking as fashion, they and their friends think this is cool, but others think it is stupid.

Make the worst case worse

I can understand the need for occasional extra effort and one or two days of overtime till midnight. However, when the boss doesn't thank you because of your efforts, but is used to it, we are in trouble. The boss wants programmers to work overtime frequently. This is not only your sorrow, but also the whole industry. Humans, like dogs, are vulnerable to both positive and negative reinforcement. The development of the entire industry is affected by the long-lived overtime and death tragedy. Until a certain stage, at that stage, such behavior is even rewarded. Every time we fall into a long debate, this trend continues to increase negatively.

This cannot help our management team. You only need to let others take the lead. Guilt brings equality-"we cannot allow our partners to do difficult things alone. We have to help ". The more people you observe, the more pressure those who leave their companions will be, until the entire team gets together for a cola and a pizza. But how can they accommodate the same people into their world, because there is also a famous programmer who is independent of each other. When we are still students, we are happy to push everything to someone to handle and then do what we want to do in school. But when we go to work, everything depends on ourselves. This is truly confusing.

Interestingly, sometimes these massive efforts are not even properly tracked, as if they make the project look bad. Therefore, they "fake accounts". Just as customers only care about the 40 hours of work per week for each person (or the 40-hour salary they get), they may also care about the current progress of the project, but they never care that every member of the group spent another 40 hours on the project. Well, maybe they will track the real efforts of recorded team members in the second set of false accounts. Although accountants will be imprisoned for such frauds, no one in the IT industry will reject such counterfeiting requirements.

Acceptable progress results

Most agile development processes will discuss acceptable development progress. However, I have also seen some teams that even think that flexible teams will spend a few hours to sit down and discuss how to make programs more efficient and reasonable, and so on, you know. Although the team members are still agile, You do not dare to say anything else.

Every time I think of this, I always think of lawyers. You are like an entry-level lawyer who has made a lot of effort and time. This is a conventional way to succeed in this industry. No programmer wants to compare with a lawyer, but the situation is often very similar, unless you don't want to make progress through long overtime (just like a lawyer, you can become a lawyer unless you work in four major consulting companies ). So which is a nerd for lawyers and programmers?

Studies on productivity declines caused by over 40 hours of work a week show disturbing regularity. As a programmer, if your creativity declines, your mistakes will increase, and you will miss the existing problems, and so on. Until a certain stage is reached, during this stage, you do more wrong things than you do right things. Should I mention health issues in particular when you spend a lot of time in the same activity. About diet, you have to rely on cola for a long time-poor John even survived less than 40 hours.

Can you tell me that I am opposed to long-time work and marching against the threat of death? Is your sleep time and sleep quality up to standard? Maybe one day I will tell you how to receive a wake-up call. This is an interesting story. Catch the cat together, it is easy to compare with the situation that allows programmers to achieve the expected results in the same direction, this is my personal (programmer) love and hate the land. However, I hope that after a while, all smart programmers will have a clear position to resolutely eliminate one of the industry trends that are very bad and against productivity. As I mentioned, smart programmers do not like long-term work or work overtime due to pressure. They spend more time enjoying their lives.

 

From:

Http://miao7616.blog.51cto.com/3258248/617009