#Task till dawn python plus#

This essentially eliminates multitasking, which is a major hurdle to staying focused and productive.

This may sound counterintuitive, but as the day wears on, the brain gets tired enough so it can only focus on a single task. A lot of times, other programmers are in different countries and time zones, so communicating in real-time often requires developers to be night owls. Most open source communication is done asynchronously through channels like mailing lists or GitHub comments. Not to mention, there's nothing like indulging in your favorite midnight snacks when you have solved a thorny problem! Communicationĭevelopers working on open source projects can have a different communication cadence than a programmer working in-house at a company.

#Task till dawn python plus#

The solitude and peacefulness, plus knowing that they'll have a few uninterrupted hours, often take the stress and time pressure associated with a daytime work schedule off their shoulders, allowing them to produce higher quality work. This allows them to be more creative and productive-especially when tackling mentally stimulating tasks such as coding. With the background noise of various activities (e.g., office chatter, traffic on the street) mostly absent at night or in the early hours, many programmers experience a sense of relaxation. Without the constant barrage of interruptions, they can spend a few solid hours focusing on the task at hand and be as productive as possible. By working at night, developers can avoid as many distractions as possible. Programming is also adversely affected by context-switching. eBook: An introduction to programming with Bashįor another, it's often not possible to program effectively in units of an hour that's barely enough time to wrap your head around the task at hand and get started.Try for free: Red Hat Learning Subscription.Having their schedules sliced into 15- or 30-minute chunks for emails, meetings, phone calls, and interruptions from co-workers is simply counterproductive. In fact, most developers have the same preference.įor one thing, developers work on large abstract systems and need the mental space to process a model in its entirety. However, there are quite a few reasons why so many programmers prefer to work during the odd hours: The maker's scheduleĪccording to Paul Graham, people who 'produce stuff' tend to adhere to the maker's schedule-they prefer to use time in units of a half-day or longer. This work habit may make many developers seem like oddballs and misfits. Some like to start in the evening and work till the early hours while others get up super early-say, 4 a.m.-to get most of the programming work done before the daily grind kicks in. This may be especially true for open source contributors who are contributing to projects outside of their day job (though hopefully within healthy limits to avoid burnout). If you ask most developers when they prefer to work, many will say their most productive hours are at night.