Dimly-lit rooms with glowing screens. Empty energy drink cans laying sideways in empty pizza boxes. The last rays of a sunset just visible out the window. Tapping keys and just-audible music highlights coming from headphones. The clock ticks well into television prime time yet no one is reaching for a coat and heading for the door.
The pop culture of programming often talks about hackathons, overnighters and crazy-long work weeks. Getting little to no sleep often becomes a developer badge of honor.
For example - Google recently offered t-shirts at its Google I/O 2016 event that had four words on the front of them:
It didn't take long for variations to appear on the market with the word sleep crossed out.
Are developers and programmers somehow immune to the need for sleep to work effectively?
In fact lack of sleep in high-tech roles has had disastrous effects:
In 1988 The National Center for Biotechnology Information published a report concerning the "role of human sleep and brain clocks in the occurrence of medical and human error catastrophes".
They found that sleep deprivation played a key role in the Challenger Accident by influencing the decision-making during a teleconference:
The effect on managers of irregular working hours and insufficient sleep “may have contributed significantly to the atmosphere of the teleconference at Marshall”The National Center for Biotechnology Information
The same report also cites lack of sleep as a probable cause in the nearly catastrophic launch of the shuttle Columbia:
Operator fatigue was reported “as one of the major factors contributing to this incident”. The operators had been on duty for 11 h. It was their 3rd day of working on a 12-h night shift.The National Center for Biotechnology Information
Why do developers end up working long and odd hours?
Long-time developer and investor Paul Graham made the case for the Maker Schedule vs the Manager Schedule.
According to Graham, the Manager Schedule is:
..for bosses. It's embodied in the traditional appointment book, with each day cut into one hour intervals. You can block off several hours for a single task if you need to, but by default you change what you're doing every hour.PaulGraham.com
But the Makers Schedule doesn't run in one hour chunks:
But there's another way of using time that's common among people who make things, like programmers and writers. They generally prefer to use time in units of half a day at least. You can't write or program well in units of an hour. That's barely enough time to get started.PaulGraham.com
Developers end up working long, odd hours because they are looking for uninterrupted blocks of time where they can focus.
Those hours can normally be found in the early morning or late night.
The allnighters can only go on so long. Hackathons are fun once a year but can't become business as usual.
Developers will burnout.
Employers and developers can each take steps to avoid burnout due to lack of sleep.
If you have a team of developers working for you, talk to them about their week to week schedules. Are they coming in early or working late? Why? How much and how often?
You need to understand the Maker Schedule, and how a single 1-hour "status update meeting" can throw off the productivity for an entire day.
Work together to establish large chunks of "meeting free zones" on the weekly calendar.
Take a fresh look at your work environment. Did you install an open floor plan to "increase communication"? Open offices can also be productivity-killers for developers who need to think deeply about their work. Many high-tech firms are going back to private offices to give their developers an environment they can do their best work in.
If a total office redesign isn't in the cards, consider creating library rules for your current setup.
Making stuff can be exhilarating:
But let's face it - it can be hard to stay healthy as a developer:
Employers can offer health plans and perks, but ultimately it's your body. It's your responsibility to find a way to do the work you love while also staying healthy.
Developers can improve their sleep habits by:
Have a project keeping you up? Maybe we can help you sleep better by pitching in on it. Contact us and we'll talk about it over some warm milk.
Lindsey serves as Omni’s Employee Experience Specialist and has 15 plus years of experience in various HR roles. Lindsey plays a key role in moving employee focused initiatives forward and she has developed our onboarding program, facilitates focus groups, implements new programs and supports our benefit offerings by answering questions from our team. She is a member of the Fox Valley Society for Human Resource Management (FVSHRM) and also the National Society for Human Resource Management (SHRM). Lindsey is married and she and her husband have their hands full with their 3-year-old son. Lindsey enjoys exploring new restaurants, spending time up north, local activities, concerts and traveling when she can.
Omni Resources is a premier custom software development firm focused on building web-based & mobile applications, business process automation and data management solutions for manufacturing, healthcare, insurance, retail and SaaS companies.