I study how humans interact with code and design new ways to build software. I work at the intersection of software engineering and human-computer interaction.


News

Our papers on Using hypotheses as a debugging aid and Find unique usages: helping developers understand common usages will appear at VL/HCC 2020.

Our paper on Explicit Programming Strategies will appear in Empirical Software Engineering.

Our paper on Mixed Human-AI Authoring of Code Patterns received a Best Paper Honorable Mention Award at VL/HCC 2019.

Our papers on Active Documentation, Mixed Human-AI Authoring of Code Patterns, and An Exploratory Study of Live-Streamed Programming appeared at VL/HCC 2019.

Our paper on Teaching Explicit Programming Strategies to Adolescents appeared at SIGCSE 2019.

I was a recipient of the NSF CAREER Award for my work on Debugging Mental Models.

My paper on Maintaining Mental Models: A study of Developer Work Habits was rated a classic by Google Scholar. CS Department news.

I gave a talk at the CS Seminar at Mason on Information Needs in Programming. It's a good overview of my research. Slides.

Join Us    I am always recruiting motivated students at all levels — undergraduate, masters, and PhD students — to support this work. Send me an email if you'd like to discuss possible opportunities.

PhD Students

David Samudio
David Samudio
Maryam Arab
Maryam Arab
Sahar Mehrpour
Sahar Mehrpour
Emad Aghayi
Emad Aghayi
Abdulaziz Alaboudi
Abdulaziz Alaboudi
Yang Yoo
Yang Yoo


Research Projects

Programming strategies
Developers solve problems by applying programming strategies, describing sequences of steps to debug, reuse, design, test, and understand code. Experienced developers work better by using more effective strategies. We've been exploring ways to capture and make explicit the strategies developers use, helping uncover how developers work differently and to create new ways to help developers benefit from the hard-earned wisdom of experienced developers.
[ESE20] [SIGCSE19]
Debugging Mental Models
As developers debug, they use their mental models to formulate hypotheses about the cause of a defect. Unfortunately, when their hypotheses are wrong, developers can waste time and get stuck gathering information that does not lead them any closer to the cause of the defect. We've conducted studies to understand how developers debug and the role of hypotheses in debugging and are exploring new forms of debugging tools which enable developers to find, use, and test relevant hypotheses from similar defects.
[VLHCC20]
Microtask Programming
Onboarding on a new project is often a long hard process, dissuading casual contributors from ever starting. What if you could contribute code to a new software project in a few minutes? How would enabling many transient contributors change software development? We've been exploring these questions through building web-based programming environments which enable microtask programming and conducting studies to understand how they change software development work.
[TSE18] [SOFTWARE16] [VLHCC15] [ICSE15] [UIST2014] [CHASE13b]
Design Rules
Good documentation has long been argued to be the key to helping developers work more quickly and consistently with design decisions. But it is left largely disconnected from code, making it hard to write and update, causing it to become out of date and untrusted, leaving developers to reverse engineer rationale from code, and causing rationale questions to be some of the most challenging to answer. We've explored the nature of this problem and the challenges developers face and have been inventing new ways to work with design decisions by capturing design rules which are bidirectionally synchronized with code.
[VLHCC19a] [VLHCC19b] [VLHCC15] [PLATEAU10] [FSE07] [ICSE06]
Information Needs in Software Development
What does this do? Will this work? Who uses this? Asking and answering questions is central to programming, software design, and coordination in programming teams. Our work has examined the most frequent questions developers ask and the challenges that they face.
[TSE15] [CHASE13a] [PLATEAU10] [CHASE10b] [FSE07] [ICSE06]
Methods for Knowing
How can we understand what software developers do? Do developer tools really help developers? In our work, we have developed methods for using field observations, lab studies, interviews, surveys, and controlled experiments to learn how developers interact with their development environments and programming languages.
[VLHCC19] [COMPUTER16] [ESE15] [PLATEAU11] [CHASE10a]
Answering Reachability Questions
What can make debugging in large and complex codebases so hard and time consuming? We found that developers ask reachability questions, searching across control flow for statements matching search criteria. For example, developers debugging a deadlock may reconstruct control flow describing where resources are acquired and released. We designed Reacher, which uses a static analysis to automate control flow searches, enabling developers to query for statements on paths and interactively construct an interprocedural control flow visualization.
[VLHCC11][ICSE10]

Resources

What do we know about human aspects of software development? Bibliography

How has software engineering research evolved over the past 4 decades? Tag Clouds

Evaluating programming languages and tools in studies with human participants Paper, Slides from tutorial