Programmer's old almanac demonstration

Get up at 8: 30 in the morning and start work at 9: 30. Go out for dinner at noon12: 30-130, maybe take a nap at 2:00-3:00. Go to 10 in the evening when you are busy, and punch in at 6: 30 in your spare time. Sleeping time depends entirely on the mood. In fact, programmers don't need that long working hours, just talk about development, if there are several hours of uninterrupted time. What you make may last for a few days. The most important thing at this stage is not to be interrupted. As for the joint debugging stage, it is better to continue to laugh. This period of time is also a time to work overtime frequently. Because you will encounter unexpected problems, both yourself and the rest of the team will drag down the overall progress. Personally, ensuring the comfort and stability of the working environment is the best way to improve work efficiency at this stage. On the day of launch, extreme overtime is prone to occur. The so-called extreme overtime refers to after midnight, or even the next morning, morning. If it's a project with a tight schedule, it's ok to work overtime on weekends. Personally, I am very opposed to working overtime on weekends: first of all, the work of programmers is very energy-consuming, and working overtime on weekends can't restore good working conditions at all; Secondly, is there any time for private life? Programmers are manual workers among mental workers, so colleagues should put health first. With health, we can make money and spend money well.