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 accessAbstract
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
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“A significant contributor to, or deterrent from, developer productivity is the time they spend seeking information to support the completion of their tasks [19,31].”
From The Evolution of Information Seeking in Software Development: Understanding the Role and Impact of AI Assistants (2025) · cites this paper as [31]
In the citing paper
“Given this, the view of developer productivity as inputs and outputs, or using metrics that strictly focus on coding, ignores the reality of the work developers do.12”
From Measuring GitHub Copilot's Impact on Productivity (2024) · cites this paper as [12]
Citations
Cites
Controlling the False Discovery Rate: A Practical and Powerful Approach to Multiple Testing
Benjamini, Y., & Hochberg, Y. (1995) · Journal of the Royal Statistical Society Series B: Statistical Methodology · doi:10.1111/j.2517-6161.1995.tb02031.x · Cited by 109,482
(1998) · Sage eBooks · Cited by 38,631
How Many Interviews Are Enough?: An Experiment with Data Saturation and Variability
Guest, G., Bunce, A., & Johnson, L. (2006) · Field Methods · doi:10.1177/1525822x05279903 · Cited by 20,808
(2014) · Cited by 15,747
The Practice of Social Research
Neustadtl, A., & Babbie, E. (1989) · Teaching Sociology · doi:10.2307/1318433 · Cited by 14,398
Five misunderstandings about case-study research
Flyvbjerg, B. (2006) · Qualitative Inquiry · doi:10.1177/1077800405284363 · Cited by 14,266
Stereotype threat and the intellectual test performance of African Americans.
Steele, C. M., & Aronson, J. (1995) · Journal of Personality and Social Psychology · doi:10.1037/0022-3514.69.5.797 · Cited by 9,020
The Practice of Social Research.
Williams, D. G., & Babbie, E. R. (1976) · Contemporary Sociology · doi:10.2307/2062956 · Cited by 7,194
What good are positive emotions?
Fredrickson, B. L. (1998) · Review of General Psychology · doi:10.1037/1089-2680.2.3.300 · Cited by 6,066
The Psychology of Survey Response
Tourangeau, R., Rips, L. J., & Rasinski, K. (2000) · doi:10.1017/cbo9780511819322 · Cited by 4,734
Research works printed but not linked: 8
- 10.1037/0021-9010.80.1.29 · doi:10.1037/0021-9010.80.1.29 · Paper page
- 10.1037//1089-2680.2.3.300 · DOI · Paper page
- kim, 2019, Understanding personal productivity: How knowledge workers define, Proc CHI Conf Human Factors Comput Syst
- spencer, 2009, Card Sorting Designing Usable Categories
- 10.1177/109821400102200202 · doi:10.1177/109821400102200202 · Paper page
- 10.1037//0022-3514.69.5.797 · DOI · Paper page
- 10.1002/(SICI)1099-1379(199607)17:4<329::AID-JOB754>3.0.CO;2-B · DOI · Paper page
- 10.1007/978-1-84800-044-5_3 · DOI · Paper page
Cited by
"How Was Your Weekend?" Software Development Teams Working From Home During COVID-19
Miller, C., Rodeghero, P., Storey, M., Ford, D., & Zimmermann, T. (2021) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse43902.2021.00064 · Cited by 142
Self-citationMeasuring GitHub Copilot's Impact on Productivity
Ziegler, A., Kalliamvakou, E., Li, X. A., Rice, A., Rifkin, D., Simister, S., Sittampalam, G., & Aftandilian, E. (2024) · Communications of the ACM · doi:10.1145/3633453 · Cited by 124
Emotions and Perceived Productivity of Software Developers at the Workplace
Girardi, D., Lanubile, F., Novielli, N., & Serebrenik, A. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3087906 · Cited by 111
“Along the same line, a recent field study at Microsoft investigated what makes a working day a good day for software developers [7].”
BackgroundMethodInfluentialThe Daily Life of Software Engineers During the COVID-19 Pandemic
Russo, D., Hanel, P. H. P., Altnickel, S., & van Berkel, N. (2021) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip52600.2021.00048 · Cited by 67
“[16] are in relative terms but not absolute terms.”
BackgroundMethodInfluentialDo you Really Code? Designing and Evaluating Screening Questions for Online Surveys with Programmers
Danilova, A., Naiakshina, A., Horstmann, S. A., & Smith, M. (2021) · International Conference on Software Engineering · doi:10.1109/icse43902.2021.00057 · Cited by 80
“Furthermore, Meyer et al. [40], when conducting a study on job satisfaction and productivity of software developers, directly recruited employees from Microsoft to ensure that all participants indeed work as software developers.”
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
- Semantic Scholar
- 50bc3089ab76042c43ac9172a6e5e7c22eae13c2
- 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
- green
- www.zora.uzh.ch
- Licence
- 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.