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

Investigating and Designing for Trust in AI-powered Code Generation Tools

Open access
Wang, Ruotong, Cheng, Ruijia, Ford, Denae, Zimmermann, Thomas·2024·The 2024 ACM Conference on Fairness, Accountability, and Transparency

Abstract

Trust is a crucial factor for the adoption and responsible usage of generative AI tools in complex tasks such as software engineering. However, we have a limited understanding of how software developers evaluate the trustworthiness of AI-powered code generation tools in real-world settings. To address this gap, we conducted Study 1, an interview study with 17 developers who use AI-powered code generation tools in professional or personal settings. We found that developers’ trust is rooted in the AI tool’s perceived ability, integrity, and benevolence, and is situational, varying according to the context of usage. Existing AI code generation tools lack the affordances for developers to efficiently and effectively evaluate the trustworthiness of AI-powered code generation tools. To explore designs that can augment the existing interface of AI-powered code generation tools, we explored three sets of design concepts (suggestion quality indicators, usage stats, and control mechanisms) that derived from Study 1 findings. In Study 2, a design probe study with 12 developers, we investigated the potential of these design concepts to help developers make effective trust judgments. We discuss the implication of our findings on the design of AI-powered code generation tools and future research on trust in AI.

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/3630106.3658984

Cites

66 of 67 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?

  • Frustration is caused both by insufficient help and invasive and premature suggestions not aligned with developers' intentions.

    “Wang et al. [34] report that frustration is caused both by insufficient help and invasive and premature suggestions not aligned with developers' intentions.”

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

  • Before a prompt reaches Copilot's filter, two hard-coded rules prevent prompts containing fewer than 10 characters and prompts where the cursor is in the middle of a line (checked by whether there is whitespace after the cursor), except when a closing character such as a closing bracket, quote, or semicolon is on that line.

    “Before a prompt reaches the filter, two hard-coded rules prevent (1) prompts containing fewer than 10 characters, and (2) prompts where the cursor is in the middle of a line, by checking whether there is whitespace after the cursor; except if there is a closing character on that line, such as a closing bracket, quote, or semicolon.”

    From A Transformer-Based Approach for Smart Invocation of Automatic Code Completion (2024) · cites this paper as [41]

    Split into 2 atoms — 0 confirmed, 0 partially supported, 0 disputed, 0 misattributed, 2 unverifiable. Expand the claim to see per-atom verdicts.

    Experimental — accuracy not yet measured
  • Copilot's filter uses a logistic classifier whose features are those listed in Table 6 (as investigated for version v1.57.7193, June 2022).

    “Based on [41], we investigated the v1.57.7193 (June 2022) version of Copilot and list the features used in their logistic classifier in Table 6.”

    From A Transformer-Based Approach for Smart Invocation of Automatic Code Completion (2024) · cites this paper as [41]

    Section F (p. 22) describes Copilot’s code-generation features as of July 2022, but does not discuss a filter or logistic classifier. Searches for the classifier, Table 6 features, and version v1.57.7193 found no passage in our copy addressing those details. (LLM, conf=0.76)

    Experimental — accuracy not yet measured

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: 2

  1. [40][40] Xiao Ma, Swaroop Mishra, Ariel Liu, Sophie Su, Jilin Chen, Chinmay Kulkarni, Heng-Tze Cheng, Quoc Le, and Ed Chi. 2023. Beyond ChatBots: ExploreLLM for Structured Thoughts and Personalized Model Responses. arXiv preprint arXiv:2312.00763 (2023). - · arXiv
  2. [51][51] Xinyue Shen, Zeyuan Chen, Michael Backes, and Yang Zhang. 2023. In ChatGPT We Trust? Measuring and Characterizing the Reliability of ChatGPT. https://arxiv.org/abs/2304.08979v1 - · arXiv

Cited by

Sorted by citations

Authors
Wang, R., Cheng, R., Ford, D., & Zimmermann, T.
Affiliations
  • University of Washington (US)
  • Microsoft (United States) (US)
Venue
The 2024 ACM Conference on Fairness, Accountability, and Transparency
Publisher
ACM
Published
2024-06-03
Pages
1475-1493
OpenAlex
W4399361983
Cited by
87
References
62
Citations by year
2026: 32 · 2025: 38 · 2024: 17
FWCI
33.13
Type
conference paper
Language
en
Open access
Locations
  • ACM Conference on Fairness, Accountability, and Transparency (FAccT) (publishedVersion, cc-by)
  • arXiv (Cornell University) (submittedVersion, cc-by)
  • arXiv (Cornell University) (cc-by)
Funders
  • Microsoft Research
  • University of Washington
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
trust in AI, developer trust, trust evaluation, situational trust, trust indicators, usage statistics, control mechanisms

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