Developer productivity and AI · Peer-reviewed empirical study or research synthesis
Software developers' perceptions of productivity
Meyer, A. N., Fritz, T., Murphy, G. C., & Zimmermann, T. (2014). Software developers' perceptions of productivity. Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE 2014).
Plain-English take
Developers perceive days as productive when completing many or large tasks without significant interruptions/context switches, although substantial task/activity switching can coexist with feeling productive. Founder-use interpretation: Useful for product/engineering workflow hypotheses and user research, not proof that a tool improves delivery metrics; pair perceived productivity with cycle time, quality, and wellbeing measures.
How much weight to give this
3.5/5 Useful empirical or synthesis evidence with context-specific transfer limits
The 1–5 evidence-check score is a practical reading aid, not a formal peer review or a probability that a conclusion is true. It combines design strength (2 points), sample reporting (1), comparison/control clarity (1), and how much of the paper could be checked (1). Access affects how confidently this directory can assess a study, not the study's underlying quality. Blinding is reported separately because it is not relevant to every design.
Scored from the described study design; an analytical or review design is not treated as a randomized field estimate.
The setting and reported sample detail are stated explicitly; size alone does not establish representativeness.
The reported comparison or synthesis method is described from the retrieved article record.
A publisher page or abstract was directly retrieved; full methods access was not established.
Double-blind? Blinding is not stated in the publisher record reviewed; that does not establish whether blinding was or was not used.
Research question
What the authors investigated
How do professional software developers perceive productive and unproductive work?
Design
Two studies, including a survey and an observational study, examining professional developers' perceptions of productive and unproductive work.
Sample and setting
Two studies, including a survey and an observational study, examining professional developers' perceptions of productive and unproductive work.
Reported result
What the study found
Developers perceive days as productive when completing many or large tasks without significant interruptions/context switches, although substantial task/activity switching can coexist with feeling productive.
This is a paraphrase of the source. Check the original paper for definitions, estimates, statistical uncertainty and analysis details.
Scope and transfer
Limitations to keep in view
Perceived rather than objective productivity; observational/self-report bias; developer and workplace context may not represent all teams.
Possible founder application
Useful for product/engineering workflow hypotheses and user research, not proof that a tool improves delivery metrics; pair perceived productivity with cycle time, quality, and wellbeing measures.
Evidence access
Publisher abstract or article landing page captured; full-text access not established.
Publisher article page directly retrieved with Firecrawl (reference 01a122bc-2599-72ce-b1ae-8d126dcda4a4). The annotation follows the retrieved title/abstract or landing-page record; full methods and correction notices were not independently reviewed.
If only an abstract or metadata was available, the profile is limited to claims supported there. A paper's paywall does not change its evidentiary status, but it limits what we can substantiate from accessible text.