How do copilot suggestions impact developers’ frustration and productivity?

Abstract Context AI-based development tools, such as GitHub Copilot, are transforming the software development process by offering real-time code suggestions. These tools promise to improve the productivity by reducing cognitive load and speeding up task completion. Previous exploratory studies, however, show that developers sometimes perceive the automatic suggestions as intrusive. As a result, they feel like their productivity decreased. Objective We propose two theories on the impact of automatic suggestions on frustration and productivity. First, we hypothesize that experienced developers are frustrated from automatic suggestions (mostly from irrelevant ones), and this also negatively impacts their productivity. Second, we conjecture that novice developers benefit from automatic suggestions, which reduce the frustration caused from being stuck on a technical problem and thus increase their productivity. Method We conducted a quasi-experimental study with 33 developers (16 experts and 17 novices). Each participant performed two Java maintenance tasks under two interaction modes: automatic suggestions enabled (proactive) and automatic suggestions disabled (reactive, on-demand). We collected IDE-level interaction traces via a custom plugin, post-task questionnaires, and physiological signals ( i.e., heart rate variability) via a wearable device. We use statistical hypothesis tests and models to study the effects of the treatments ( i.e., automatic suggestions enabled/disabled) on the outcomes (frustration and productivity). Results The aim of our work is to corroborate or contradict our theories with empirical evidence collected in a quasi-experimental study. Conclusions The results corroborate both our experience-dependent theories. Novice developers benefit from proactive suggestions, showing lower frustration and higher productivity when automatic suggestions are enabled. Instead, expert developers benefit from reactive, on-demand interaction: disabling automatic suggestions is associated with lower frustration and higher productivity. Our findings motivate adaptive interaction strategies that tailor proactivity to developer experience, balancing proactive guidance for novices with control-preserving, user-invoked assistance for experts.

Authors

Institutions

Publication Details

Journal
Empirical Software Engineering
Published
2026-11-03
DOI
https://doi.org/10.1007/s10664-026-10965-6
Citations
1
Primary Topic
Software Engineering Research
Type
article
Field-Weighted Citation Impact
4.54
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

How do copilot suggestions impact developers’ frustration and productivity?

Rocco Oliveto, Gabriele Bavota, Simone Scalabrino, Emanuela Guglielmi et al.
1 citations
Empirical Software Engineering
Software Engineering Research
4.54
article

How do copilot suggestions impact developers’ frustration and productivity?

Rocco Oliveto, Gabriele Bavota, Simone Scalabrino, Emanuela Guglielmi, Venera Arnoudova
article en
1 citations

Abstract

Abstract Context AI-based development tools, such as GitHub Copilot, are transforming the software development process by offering real-time code suggestions. These tools promise to improve the productivity by reducing cognitive load and speeding up task completion. Previous exploratory studies, however, show that developers sometimes perceive the automatic suggestions as intrusive. As a result, they feel like their productivity decreased. Objective We propose two theories on the impact of automatic suggestions on frustration and productivity. First, we hypothesize that experienced developers are frustrated from automatic suggestions (mostly from irrelevant ones), and this also negatively impacts their productivity. Second, we conjecture that novice developers benefit from automatic suggestions, which reduce the frustration caused from being stuck on a technical problem and thus increase their productivity. Method We conducted a quasi-experimental study with 33 developers (16 experts and 17 novices). Each participant performed two Java maintenance tasks under two interaction modes: automatic suggestions enabled (proactive) and automatic suggestions disabled (reactive, on-demand). We collected IDE-level interaction traces via a custom plugin, post-task questionnaires, and physiological signals ( i.e., heart rate variability) via a wearable device. We use statistical hypothesis tests and models to study the effects of the treatments ( i.e., automatic suggestions enabled/disabled) on the outcomes (frustration and productivity). Results The aim of our work is to corroborate or contradict our theories with empirical evidence collected in a quasi-experimental study. Conclusions The results corroborate both our experience-dependent theories. Novice developers benefit from proactive suggestions, showing lower frustration and higher productivity when automatic suggestions are enabled. Instead, expert developers benefit from reactive, on-demand interaction: disabling automatic suggestions is associated with lower frustration and higher productivity. Our findings motivate adaptive interaction strategies that tailor proactivity to developer experience, balancing proactive guidance for novices with control-preserving, user-invoked assistance for experts.

Empirical Software EngineeringVol. 32(2)
University of Molise (IT), Università della Svizzera italiana (CH), Washington State University (US)
Openalex Percentile: Top 9%
Software Engineering Research
4.54
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon