Developer experience · Large-scale quantitative and qualitative empirical industry study at Microsoft, investigating engineers' change-understanding work, information needs, and tool requirements.
How Do Software Engineers Understand Code Changes? An Exploratory Study in Industry
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering (FSE '12) · 2012
Summary
Understanding changes is indispensable, but engineers struggle to obtain completeness, consistency, and especially risk information. Composite changes are easier to understand when decomposed into issue-aligned sub-changes, yet current tools provide inadequate decomposition support.
For your marketing
Possible founder application
Build IDE, pull-request, and change-intelligence features that expose rationale, completeness, consistency, dependency risk, and issue-aligned decomposition; measure time-to-understanding and information gaps as developer-experience outcomes.
Reported result
What the study found
Understanding changes is indispensable, but engineers struggle to obtain completeness, consistency, and especially risk information. Composite changes are easier to understand when decomposed into issue-aligned sub-changes, yet current tools provide inadequate decomposition support.
Research question
What the authors investigated
What role does understanding code changes play in software development, what information do engineers need, and what tool support do they require?
Design
Large-scale quantitative and qualitative empirical industry study at Microsoft, investigating engineers' change-understanding work, information needs, and tool requirements.
Sample and setting
Microsoft software engineering industry setting; the accessible publisher abstract describes a large-scale quantitative and qualitative study but does not state participant or artifact counts, so no count is inferred here.
Scope and transfer
Limitations to keep in view
The abstract identifies one industrial setting and reports an exploratory study; the accessible page does not provide enough detail to assess all sampling, measurement, or causal limitations. Findings may not generalize to other organizations or development processes.
Research sources
Title, authors, venue, year, DOI and pages: https://doi.org/10.1145/2393596.2393656; abstract and study description: https://www.microsoft.com/en-us/research/publication/how-do-software-engineers-understand-code-changes-an-exploratory-study-in-industry/ Firecrawl research job 01a14371-854f-71aa-ba3d-455ec397717d returned this citation and metadata.