Why working at night doesn’t work

Lots of programmers insist on working late. That’s a bad idea. For every one time a programmer reaches “flow” state and effortlessly produce reams of brilliant code late at night, there are a hundred inefficient programming sessions with low productivity and high error rates.

In most organizations, it is a near certainty that you will be spending most of your day doing something other than what you had planned. Most solutions involve company culture, managers, scrum masters, and colleagues. But there is one solution that is completely within your control: Show up early and complete one important task.

If it’s your job to eat a frog, it’s best to do it first thing in the morning. And If it’s your job to eat two frogs, it’s best to eat the biggest one first.
Mark Twain

If you are a night owl like me, that might be a significant change to your life. But it pays off handsomely in more happiness and less stress. Stress is caused by a feeling that you are not in control of your situation; starting early and actually getting a task of your own choosing done each day defeats this feeling.

Try starting work two hours earlier than everybody else for two weeks and see how much more you get done.