Programmer misunderstanding 2: working overtime and staying up late for software development

☆★☆★Come on !! October 25 reader meeting ☆★☆★

 

Tsinghua University Press JavaProgramStaff, working hours by Bell

A layman's boss:
A friend of mine works in an internationally renowned company. The Chinese company in Beijing is controlled by a domestic e-commerce company.
Recently, the company made personnel adjustments, and the former Foreign Management was replaced by the Chinese management.
The new Chinese management personnel are former managers in other industries and are not an expert in the IT industry. They have promoted multiple work styles since taking office, one of which is, software technicians must work from.
The "8-Hour" work system identified by the company's management system is just an empty one. Of course, you can leave the company at a.m., but soon you will receive an email for name criticism.

This is a joke that a layman leads an expert. Obviously, the CEO's idea is: "How can I not work overtime in software technology? Don't stay up late ?"
His idea is precisely a misunderstanding of his career: "software development must work overtime and stay up late ".

2.2.1 excuses for programmers to stay up late

This misunderstanding of the software development profession is not "a plug-in", because we do see many programmers working overtime and staying up late in companies without rigid regulations.
It is this phenomenon that the onlookers naturally think of the assumption that "programmers need to work like this. As a programmer, "overtime" exists, but this "Phenomenon" itself is "accidental" and cannot be a "normal ".
Programmers can always find an excuse to stay up late for work. Let's take a look at what is there.

2.2.1.1CodeIn one breath, be sure to finish writing and then fast

Programming in one breath is the main driving force for most programmers to work overtime. For example, when Mr. Zhang develops a graphic display component, the component program is close to the end, and he must finish writing it and see the desired effect before he can stop.
The motivation for working overtime comes from the programmers themselves. The enthusiasm for this kind of work comes from the enthusiasm of the programmers for their work. This phenomenon is helpful to programmers and the entire project team. It should be encouraged, but it should not be "normal ".

2.2.1.2 make a proposition demonstration tomorrow. Make sure to debug the program.

I am eager to give a program demonstration of the proposition to the customer tomorrow, but I am not finished yet. I am so anxious to catch my ears. At this time, I am not working overtime yet? The major account ran away, and this responsibility could not afford. Therefore, it must have been done before we can go home. We will light up tomorrow and complete the demonstration smoothly.

2.2.1.3 Quiet Working Environment

We also heard programmers complain that there is no quiet working environment. Generally, there are two aspects:
First, programmers not only need to write programs, but also spend time reading and replying emails, answering phone calls to handle various questions, assisting HR interviews, and even reviewing product user manuals, there is no way to write the code in one breath.
Second, it comes from the surrounding environment. If the programmer is lucky enough to be a neighbor with the business department or customer service department, the problem still exists, because the telephone and conversation there are one after another.

In the face of these two problems, we should have their own solutions:
In the first case, you should arrange your work schedule and allocate your time as much as possible.
In the second case, apply for a change of seats or a quiet like water.

2.2.1.4 the project is in a tight schedule and the task needs to be completed as soon as possible

"Tight project progress" is often an excuse for "overtime". On the one hand, it is an excuse for project managers to ask programmers to work overtime, and on the other hand, it is an excuse for programmers who are dragging their jobs.
The reason for this is that the direct responsibility for "project progress shortage" should be attributed to "project managers" rather than "programmers ". The project progress should be reasonably arranged and allocated by the "Project Manager". What "programmers" need to do is to complete coding according to the project progress requirements, if the coding work is completed according to the established plan, the shortage of project progress is naturally a problem of project management.
However, there is another phenomenon: the "Project Manager" has a proper schedule, and some programmers are procrastinating in their work, and they are doing other things without finishing their tasks, this leads to project progress shortage and "overtime ".
Therefore, it must be an "alarm" for overtime Due to this reason, that is, "a problem occurs in the project". Therefore, this Overtime must be avoided.

Working overtime due to tight project schedule:
It is a signal of a project or your own problems.

2.2.2 dangers of normal overtime

Accidental overtime does not affect the programmer's work enthusiasm. However, overtime becomes the norm, which can cause great harm to your work.

2.2.2.1 hazard 1: The project progress does not rise or fall

After working overtime becomes the norm, especially when the boss asks him to work for more than 12 hours, you will find that programmers arrange personal affairs for work hours. When should programmers handle their own private affairs?

2.2.2.2 hazards 2: The work enthusiasm has been seriously negotiated

Working overtime is a positive expression of work, especially for programmers who work overtime due to "code in one breath", it is also a manifestation of the hard work of the company for the project. However, when companies require overtime rather than spontaneous overtime, the enthusiasm of these programmers can be fully negotiated.

2.2.2.3 Hazards 3: physical hazards to programmers

8 hours of work is relatively scientific and reasonable. If you try to use your body desperately, it will definitely damage your body, which will inevitably lead to problems such as hard work and poor memory, the response is not agile, and so on. The damage these phenomena cause to the project is even more fatal.

Normal overtime brings great harm. Experienced project managers or wise managers won't allow this phenomenon, and where to find the cause of the problem, do not increase the working hours to make up for the real vulnerabilities.
As a new programmer, you must also be aware of these dangers and not fall into the misunderstanding of "working overtime and staying up late.

2.2.3 controlling the daily work schedule is the key

As mentioned above, programmers not only need to write programs, but also spend time reading and replying emails, answering phone calls to handle various questions, assisting HR interviews, and even reviewing product user manuals, there is no way to write the code in one breath in one go, and the coding problem cannot be ensured during the day.
Our programmers should set a "one-day schedule" for themselves. This one-day schedule can arrange the time more reasonably and focus on the most important things.

For example, the following timetable can be used as a reference:
Take over a cup of hot water, turn on the computer, sort out ideas, read and reply to emails received after work last night-0.5 hours
Focus on software development-2.5 hours
Lunch break-45 minutes
Read and reply to the email-15 minutes
Focus on software development-4 hours
Handle other transactions, such as phone calls-1 hour
Read and reply to the email-10 minutes

Before arriving at the company early in the morning, the 2.5 hours before lunch were the most efficient time period of the day. During this time period, we should be fully engaged in development work. During this time, our minds were clear and our thinking was agile, avoid doing other things as much as possible. You will find that the development progress at this time will get twice the result with half the effort.
Next, take a break after lunch. You can process the email as soon.
Later, the development time entered the afternoon, the most efficient part of this time period is 2.5 hours, try to put all the energy into coding within 2.5 hours.
Phone calls and other transactions will be interspersed in the afternoon's working hours, and should be compressed within 1 hour as much as possible.
Finally, read and reply to the email before leaving work.
As you can see, isn't it difficult to get confused by other complicated tasks? Do you need to work overtime to process development tasks with the highest efficiency and emails with close breaks or close to work hours?
On the contrary, if a single line of code is not written during the whole day, it will not work without working overtime.

Time Policy:
Good steel is used on the blade.

2.2.4 "paranoia and fanaticism" is not equal to working overtime

If a programmer wants to succeed, he needs the power of "paranoid and fanatic", which forces the programmer to stay at the forefront of the latest technology forever, focus on the implementation methods of the latest products.
Intel's president, Andy Grove, said, "Only being paranoid can be successful." He decided on a belief that he had been disdainting and eventually went to the other side of success. For programmers, this "fanatic and paranoid" is a process of continuous efforts. First, it becomes a "enthusiast" of software development technology and positions itself in the form of international and domestic technologies.
This process is difficult, but it is not equal to the infinite stacking of "workload", not to achieve its goal by extending the working hours. This process is ongoing exploration and thinking.
Fanatics do not mean working overtime. They need to think rationally, broaden their horizons, and make continuous efforts.

Fanatic and paranoid:
Emphasize the importance of thinking, rather than extending work hours.

《Java programmers, work",Preface,Directory