You desperately write code your boss has thanked you?

Programmers seem to be keen on working long hours. But what I'm trying to say is, you admit it, your job or your boss didn't actually let you do it, you just have to do it yourself. Of course, I also know that maybe not all programmers like long time programming. But what I can be sure of is that when overtime becomes a common phenomenon in the industry, at least half of the programmers have to love to work overtime.

I have long been tired of the following kinds of excuses. "No, it's not that, we just love cool tech, and we don't want to leave unresolved problems behind." In fact, overtime is a good thing because it makes us better! "

But I think you can't just see trees and trees. And from a certain point of view, you're not doing it for yourself, just for someone. Don't question, maybe He's a noble man, but obviously you're not his slave. In other ways, how many times do you have to work overtime to solve problems, to study new technologies, to encode something, and to finish a task before the deadline? But you're a savvy programmer in business, and you're helping the company to achieve success. Company managers have told you about the company's economic situation--it has to be done, and the company relies on you. What I want to say is that unless the manager is right next to you and chatting with you at 2 O ' night, his words will be worthless.

Let me tell a story that a friend once told me. This story is about a gifted programmer, let's call him John.

John is a superstar among millions of programmers. His ability to understand and write code is superb, and the efficiency is 20 times times that of anyone else. One day, the company got a big project for short delivery. The customer provided a specification that was so thick that everyone was frustrated. John helped, and he took the instructions home, and no one had heard from him for three days thereafter. When he came back to work, he looked very gaunt, but he read the whole manual and completed the basic framework of the project. In addition to a small number of impossible to complete, the rest of the manual, and even customers do not understand the requirements, John also completed. That's amazing!

When I first heard about the story, I felt so deep, I asked the first question, "Where is John now?" My friend replied, "He's dead, life is too hard!" Perhaps it is more appropriate to use the program to describe the death of overwork. The story is surprising that--john is only 30 years old.

Programmers get perverse pleasure from sharing death stories. Even when we do so with disgust, this aversion is accompanied by a hint of pride that encourages colleagues to do better. But it's kind of like those guys in shorts, their shorts are short enough for you to see their underwear, and they're kind of like people who smoke as fashion, and they and their friends think it's cool, and others feel stupid.

Make a bad situation worse

I can understand the need for occasional extra effort and one or two days ' overtime to midnight. However, when occasionally become often, when the boss no longer because of your efforts and often thank you, but accustomed to, we have trouble. The boss wants programmers to work overtime, which is not only your sadness, but the industry as a whole. Humans, like dogs, are very susceptible to positive and negative reinforcement. The development of the industry has been affected by the tragic death of overwork over the years, until at some stage it is even rewarded. Every time we get into a long argument, this trend continues to be negatively exacerbated.

It doesn't help us manage the team. You just have to let one person decide, and others to follow. Guilt brings equality-"We can't let our partners do the difficult things alone, we have to help." The more people you follow, the more pressure people will have to leave their peers, until the whole team gets together in the middle of the night drinking Coke and eating pizza. But how they can accommodate a similar person into their world, because there is also a well-known as a maverick programmer. When we are students, we are happy to push everything to someone and then do what we want to do in school, but when we go to work, everything depends on us. That's confusing.

Interestingly, sometimes these massive efforts don't even get a normal track record, as if it makes the project look bad. So they "cheat the books", just as customers care that everyone works 40 hours a week (or they get 40 hours), and may also be concerned about the project's current schedule, but they never care about the other 40 hours that each team member spends on the project. Well, maybe they'll track the real effort of the team members in the "second set of accounts". Although accountants will be jailed for such fraud, no one in the IT industry will object to the false claims.

Acceptable Progress Results

Most agile development processes will discuss acceptable development progress. However, I've also seen some people who think they're flexible enough to sit down together for a few hours to talk about how to make a program more efficient and reasonable, and so on, you know. Although team members are still thinking agile, you dare not say anything else.

Whenever I think of this thing, I always think of lawyers. You are like an entry-level lawyer who has paid a lot of effort and time, which is a routine way to succeed in this industry. No programmer wants to compare with a lawyer, but the situation is often similar, unless you don't want to make progress in the same way as a program developer through long hours of overtime (like a lawyer, unless you work in a 4-strong consulting firm, you can become a lawyer). So, lawyers and programmers, which one is a nerd?

Research into the decline in productivity over 40 hours of work a week presents disturbing regularity. As a programmer, if your creativity declines, your mistakes increase, you omit existing problems, and so on, until you reach a certain stage where you're doing the wrong thing more than doing the right thing. When you spend a lot of time in the same activities, should I mention health issues in particular? About diet, you can only survive for a long time with cola-poor John even survived less than 40 hours.

Are you aware of my opposition to long hours and death threats? Have you reached your sleep time and sleep quality? Maybe one day I'll tell you how I got the wake-up call (Wake Upcall), which is an interesting story. It's easy to get a cat together, and it's easier to compare it with the results of the programmer in the same direction that I love and hate for our people (programmers). But I hope that after a while, all smart programmers need a clear stance and resolutely eliminate one of the worst and most unproductive trends in the industry. As I mentioned, smart programmers don't like to work long hours, or because they are pressured into working overtime, and they spend more time enjoying life.