Thoughts on overtime

I have seen these two articles recently.ArticleI feel a lot of emotion.

Based on my recent work experience, I feel that the two articles are too well written.

Those who often advocate "positive energy", just skip it. The three concepts to express below are different from yours.

Who is letting our programmers work overtime?

"Who is on us?ProgramStaff overtime?

Company? Boss? Boss? Other programmers?

It is actually possible.

There are also many times that companies do not have this requirement, but some of the flaws are the performance of love. 

 

After the project is completed, you have completely lost this employee. Realizing that a person sacrifices more important values (family, love, family, and youth) for unimportant values (work) is destructive, it will make a person who has made a sacrifice without any knowledge seek revenge ....

When people are overwhelmed by time, they do not work better, but work faster.
To work faster, they have to sacrifice product quality and their satisfaction with their work ."

 

Why is China's low programmer technology?

 

Conclusion:

[Programmers caused by overtime and other factors] passive, weak, unsubjective, hypocritical, unpromising, unordered, resentful, hypocritical, less time to study, no planning,CodeThe quality is low, the work is in disorder, the technology is always at the "hitting" level, the skill industry is not specialized, low-key, confused, the mentality is unstable, the mind is wandering, the life is difficult, the development is difficult, the maintenance is difficult, the pressure big, hard to communicate, dissatisfied, passive, unable to afford to put down, dilemma.

The above phrases summarize the character, mentality, living environment, and working environment of programmers. They are just like toxins, and can destroy a healthy programmer for a long time. In this environment, why is your technology so low? That's funny.

Unfortunately, the current project is almost fully compatible with the descriptions described in the two articles ....

A group of people from various places are gathered together to catch up on the progress. There is no planning in the early stage, which leads to the re-engineering of the project.

People have different working backgrounds and different habits. They do not have uniform standards. They make and modify the previous things.

Almost only a few people have good development habits. They will be able to take the server configurations and hold them all over again.

Most people do not have good SVN usage habits. Submitting and not writing logs is common and SVN show log has no reference information.

Overtime means low efficiency, and some of them are "Miscellaneous". They are often added to the middle of the night, and there is nothing to do during the day, so they are very inefficient at night,

Working overtime on the first day will start from the afternoon.

I can understand it without a trial period, but I think this kind of work is glorious and show off repeatedly, which has a very bad impact on others.

Overtime also means that the project does not have a namespace because the code is not abstract, the reusability is poor, the coupling is strong, and there is no log.

Some people are still stuck at the event-driven level. It is not easy to write so many businesses after such a long time.

The sources of personnel are complicated. The lower the level, the higher the popularity. If you have a slight side-by-side question about code encapsulation, you will immediately experience a strong rebound.

People with poor back-end planning, lack of architects, and poor levels are self-righteous, poor architecture, and omissions,

However, because this person worked overtime, he held the right to speak. Others were too "low-key" and the whole was in a low-level development environment.

To sum up:

People who work overtime are often appreciated by their superiors and think they have a good working attitude and can sell their lives. Will be important. However, long-term overtime is definitely the cause and result of low efficiency.

It is hard to imagine a person who can give up his or her own life and do not care about his or her family. What is his or her sense of responsibility for other things. Even if it can play a certain role in the project progress for the time being, but in the long run,

The company and team are all very harmful. Aside from this, the impact on his own health and even life is even more direct.

It is terrible for programmers who actively work overtime.

This inefficient way of working is like a source of pollution, destroying the atmosphere of the entire team, and those who have the ability to not work overtime will surely stay away from it.

As you can see, all overtime teams will not have a good atmosphere, dull, depressing, low-profile, no responsibility, and cowardly is the tone,

Those who do not have the ability to work overtime cannot get a normal rest. They often have to spend time with those who are used to staying up late.

Those who only focus on their own performance never realized their influence on the entire team atmosphere and the pressure on other normal people.

As a result, anyone who sacrifices their time and lives due to overtime will be released to the team. Even normal programmers will soon become grumpy and impatient.

In this atmosphere full of negative energy, the following levels and low production capacity are almost inevitable.

 

The complaint is over and the score is reduced a lot. We hope that we do not want to have sex with programmers who work overtime, but to use our own abilities and creativity to create value through healthy and active work.