Cited by 213Software Engineering ResearchSoftware Engineering Techniques and PracticesUsability and User Interface Design

A Large-Scale Survey on the Usability of AI Programming Assistants: Successes and Challenges

Open access
Liang, Jenny T., Yang, Chenyang, Myers, Brad A.·2024·Proceedings of the IEEE/ACM 46th International Conference on Software Engineering

Abstract

The software engineering community recently has witnessed widespread deployment of AI programming assistants, such as GitHub Copilot. However, in practice, developers do not accept AI programming assistants' initial suggestions at a high frequency. This leaves a number of open questions related to the usability of these tools. To understand developers' practices while using these tools and the important usability challenges they face, we administered a survey to a large population of developers and received responses from a diverse set of 410 developers. Through a mix of qualitative and quantitative analyses, we found that developers are most motivated to use AI programming assistants because they help developers reduce key-strokes, finish programming tasks quickly, and recall syntax, but resonate less with using them to help brainstorm potential solutions. We also found the most important reasons why developers do not use these tools are because these tools do not output code that addresses certain functional or non-functional requirements and because developers have trouble controlling the tool to generate the desired output. Our findings have implications for both creators and users of AI programming assistants, such as designing minimal cognitive effort interactions with these tools to reduce distractions for users while they are programming.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3597503.3608128

Cites

48 of 48 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

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?

  • Only 40% of CCT suggestions are accepted the first time they are proposed to developers, mainly because developers cannot control context or granularity.

    “Some recent studies confirm these symptoms: only 40% of CCT suggestions are accepted the first time they are proposed to developers, mainly because developers cannot control context or granularity (Liang et al., 2024).”

    From Understanding user mental models in AI-driven code completion tools: Insights from an elicitation study (2025) · cites this paper as Liang et al., 2024

    The Introduction (page unavailable) says developers do not accept initial suggestions at a high frequency, but gives acceptance rates of 23.3%, 27.9%, and 28.8% for GitHub Copilot suggestions—not 40%. The paper also reports difficulties controlling output and requests for better code context and adjustable suggestion length, but it does not establish that inability to control context or granularity is the main reason for the claimed first-time acceptance rate. (LLM, conf=0.87)

    Experimental — accuracy not yet measured
  • Liang et al. (2024) found that GitHub Copilot was the most widely used tool (74.6%), and its users reported a median of 30.5% of their code was generated by the AI assistant.

    “GitHub Copilot was the most widely used tool (74.6%), whose users reported that a median of 30.5% of their code was now generated by the AI assistant.”

    From Echoes of AI: Investigating the downstream effects of AI assistants on software maintainability (2026) · cites this paper as Liang et al. (2024)

    Section 4.1 reports that GitHub Copilot had the most users (306 of 410 survey respondents, or 74.6%) and that its users reported a median of 30.5% of their code was written with its help. It does not say that all of that code was generated by the assistant; “written with its help” is a broader measure. (LLM, conf=0.86)

    Experimental — accuracy not yet measured
  • Liang et al. (2024) and Butler et al. (2025) found that developers generally feel productivity gains using the same assistant.

    “Similarly, Liang et al. ( 2024) and Butler et al. (2025) found that developers generally feel productivity gains using the same assistant.”

    From Echoes of AI: Investigating the downstream effects of AI assistants on software maintainability (2026) · cites this paper as Liang et al. (2024)

    Section 4.2 (page unavailable) reports that 76% of participants who used AI programming assistants at least monthly cited finishing tasks faster as an important reason for using them. This supports a general perception of productivity benefits, but the survey covered multiple assistants and does not establish that developers felt those gains using the same specific assistant. (LLM, conf=0.84)

    Experimental — accuracy not yet measured
  • Frustration occurs when suggestions do not satisfy functional or non-functional requirements.

    “Liang et al. [18] found that frustration occurs when the suggestions do not satisfy functional or non-functional requirements.”

    From How do Copilot Suggestions Impact Developers' Frustration and Productivity? (2025) · cites this paper as Liang et al. [18]

    Section 5.5, “Giving up on outputted code” (page not available in our copy), reports that participants gave up on generated code when it failed to meet functional or non-functional requirements. It does not establish that they experienced frustration, which is the response the citing sentence attributes to the study. (LLM, conf=0.84)

    Experimental — accuracy not yet measured
  • Acceleration mode is usually preferred, as developers often use the tools to complete repetitive code that cannot be copy-pasted and for recalling syntax they don't remember.

    “Acceleration mode is usually preferred, as developers often use the tools to complete repetitive code that cannot be copy-pasted (Liang et al., 2024), and for recalling syntax they don't remember (Xu et al., 2022).”

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 5

  1. Ruijia Cheng, Ruotong Wang, Thomas Zimmermann, and Denae Ford. 2022. "It would work for me too": How online communities shape software developers' trust in AI-powered code generation tools. arXiv preprint arXiv:2212.03491 (2022). · arXiv
  2. Victor Dibia, Adam Fourney, Gagan Bansal, Forough Poursabzi-Sangdeh, Han Liu, and Saleema Amershi. 2022. Aligning offline metrics and human judgments of value of AI-pair programmers. arXiv preprint arXiv:2210.16494 (2022). · arXiv
  3. Ben Puryear and Gina Sprint. 2022. GitHub Copilot in the classroom: Learning to code with AI assistance. Journal of Computing Sciences in Colleges 38, 1 (2022), 37-47.
  4. Mohammad Tahaei and Kami Vaniea. 2022. Lessons Learned From Recruiting Participants With Programming Skills for Empirical Privacy and Security Stud- ies. In International Workshop on Recruiting Participants for Empirical Software Engineering (RoPES).
  5. Ashish Vaswani, Noam Shazeer, Niki Parmar, Jakob Uszkoreit, Llion Jones, Aidan N Gomez, Łukasz Kaiser, and Illia Polosukhin. 2017. Attention is all you need. Advances in neural information processing systems 30 (2017).

Cited by

Sorted by citations

Authors
Liang, J. T., Yang, C., & Myers, B. A.
Affiliations
Carnegie Mellon University (US)
Venue
Proceedings of the IEEE/ACM 46th International Conference on Software Engineering
Publisher
ACM
Published
2024-02-06
Pages
1-13
ISSN
0270-5257 (ISSN-L)
OpenAlex
W4391558520
Cited by
203
References
45
Citations by year
2026: 68 · 2025: 92 · 2024: 42 · 2023: 1
FWCI
76.92
Type
conference paper
Language
en
Open access
Locations
  • ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion, cc-by)
  • arXiv (Cornell University) (submittedVersion, cc-by)
  • arXiv (Cornell University) (cc-by)
Funders
National Science Foundation (1745016, 1856641, 2140739)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
Keywords
GitHub Copilot, usability, developer practices, code completion, developer motivation, non-functional requirements, cognitive effort, tool control, large language models

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