Book a call

News · December 2, 2020

GitHub's Octoverse shows longer, more flexible workdays for remote developers

// teams.news :: 2020

GitHub's annual report looked at how developers worked during a year spent largely at home. Productivity held up, but workdays stretched, which matters for anyone managing distributed engineering teams.

What happened

  • GitHub published its 2020 State of the Octoverse on December 2, 2020, with deep dives on work-life balance, community health and software security, according to its blog.
  • The report's productivity section found that pushes and pull requests per person held steady or rose compared with the prior year, and that the window between first and last push grew by 30 to 60 minutes a day for US Pacific developers from mid-March.
  • It also found that enterprise activity fell at weekends while open source activity rose, and warned that long hours at the expense of rest may not be sustainable.
  • The Register reported that developers created 35% more repositories than a year earlier and that GitHub counted over 56 million developers.

Why it matters

The data supports what many managers suspected: remote engineers ship as much or more, but the working day spreads out. Without agreed core hours and response expectations, that spread turns into always-on availability and, eventually, burnout.

For distributed and contracted teams we would set a few hours of overlap for live collaboration, keep everything else async, and track cycle time and review turnaround rather than hours online. Automating checks on pull requests, which the report links to faster merges, is a cheap win.

Sources

  • GitHub Blog: The State of the Octoverse 2020
  • GitHub Octoverse: The 2020 State of the Octoverse: Finding Balance Between Work and Play
  • The Register: COVID-19 coronavirus captive coders create copious code, claims GitHub: Open-source projects mushroom amid pandemic

This post is CMM’s own summary and commentary on publicly reported news. Facts are attributed to the sources linked above; please read them for full details. CMM is not affiliated with these publishers or with the companies mentioned, and trademarks belong to their owners. Prepared with AI assistance. Corrections or requests: [email protected]. See our editorial policy.

Want help with this?

Tell us what you need, and we will suggest the right team model on a short call.

Talk to us