Student or educator? Sign up with your school email and get 6 months of Pro free.

The DOI matches its Crossref record, with a small difference in title or year; 111 of the 113 references it cites were found in a registry or an index.

Today Was a Good Day: The Daily Life of Software Developers

Open access
Meyer, Andre N., Barr, Earl T., Bird, Christian, Zimmermann, Thomas · 2021 · IEEE Transactions on Software Engineering

Abstract

What is a good workday for a software developer? What is a typical workday? We seek to answer these two questions to learn how to make good days typical. Concretely, answering these questions will help to optimize development processes and select tools that increase job satisfaction and productivity. Our work adds to a large body of research on how software developers spend their time. We report the results from 5,971 responses of professional developers at Microsoft, who reflected about what made their workdays good and typical, and self-reported about how they spent their time on various activities at work. We developed conceptual frameworks to help define and characterize developer workdays from two new perspectives: good and typical. Our analysis confirms some findings in previous work, including the fact that developers actually spend little time on development and developers' aversion for meetings and interruptions. It also discovered new findings, such as that only 1.7 percent of survey responses mentioned emails as a reason for a bad workday, and that meetings and interruptions are only unproductive during development phases; during phases of planning, specification and release, they are common and constructive. One key finding is the importance of agency, developers' control over their workday and whether it goes as planned or is disrupted by external factors. We present actionable recommendations for researchers and managers to prioritize process and tool improvements that make good workdays typical. For instance, in light of our finding on the importance of agency, we recommend that, where possible, managers empower developers to choose their tools and tasks.

Overview

Integrity signals

Registry

Crossref · 10.1109/tse.2019.2904957

Cites

111 of 111 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Citations

Cites

Show all 113 references

Research works printed but not linked: 8

  1. 10.1037/0021-9010.80.1.29 · doi:10.1037/0021-9010.80.1.29 · Paper page
  2. 10.1037//1089-2680.2.3.300 · DOI · Paper page
  3. kim, 2019, Understanding personal productivity: How knowledge workers define, Proc CHI Conf Human Factors Comput Syst
  4. spencer, 2009, Card Sorting Designing Usable Categories
  5. 10.1177/109821400102200202 · doi:10.1177/109821400102200202 · Paper page
  6. 10.1037//0022-3514.69.5.797 · DOI · Paper page
  7. 10.1002/(SICI)1099-1379(199607)17:4<329::AID-JOB754>3.0.CO;2-B · DOI · Paper page
  8. 10.1007/978-1-84800-044-5_3 · DOI · Paper page

Cited by

See all 125

Metadata

Authors
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T.
Affiliations
  • University College London (GB)
  • Microsoft (United States) (US)
Venue
IEEE Transactions on Software Engineering
Published
2021-05-01
Volume
47
Issue
5
Pages
863-880
ISSN
  • 0098-5589 (ISSN-L)
  • 1939-3520
  • 2326-3881
OpenAlex
W2921988748
Cited by
123
References
113
Citations by year
2026: 20 · 2025: 26 · 2024: 19 · 2023: 17 · 2022: 16 · 2021: 14
FWCI
12.76
Type
journal article
Language
en
Open access
Locations
  • IEEE Transactions on Software Engineering (publishedVersion)
  • Zurich Open Repository and Archive (University of Zurich) (acceptedVersion, other-oa)
  • UCL Discovery (University College London) (submittedVersion)
  • Zurich Open Repository and Archive (University of Zurich) (submittedVersion, other-oa)
  • Zurich Open Repository and Archive (University of Zurich)
Funders
Engineering and Physical Sciences Research Council (EP/J017515/1)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Social Sciences › Decision Sciences › Information Systems and Management › Personal Information Management and User Behavior
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
job satisfaction, productivity, meetings, interruptions, email, development process optimization

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Today Was a Good Day: The Daily Life of Software Developers. https://app.cochat.ai/papers/10.1109/tse.2019.2904957
The paper
Meyer, A. N., Barr, E. T., Bird, C., & Zimmermann, T. (2021). Today Was a Good Day: The Daily Life of Software Developers. IEEE Transactions on Software Engineering. https://doi.org/10.1109/tse.2019.2904957

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.