Using AI-based coding assistants in practice: State of affairs, perceptions, and ways forward
Open accessAbstract
Context. The last several years saw the emergence of AI assistants for code - multi-purpose AI-based helpers in software engineering. As they become omnipresent in all aspects of software development, it becomes critical to understand their usage patterns. Objective. We aim to better understand how specifically developers are using AI assistants, why they are not using them in certain parts of their development workflow, and what needs to be improved in the future. Methods. In this work, we carried out a large-scale survey aimed at how AI assistants are used, focusing on specific software development activities and stages. We collected opinions of 481 programmers on five broad activities: (a) implementing new features, (b) writing tests, (c) bug triaging, (d) refactoring, and (e) writing natural-language artifacts, as well as their individual stages. Results. Our results provide a novel comparison of different stages where AI assistants are used that is both comprehensive and detailed. It highlights specific activities that developers find less enjoyable and want to delegate to an AI assistant, e.g., writing tests and natural-language artifacts. We also determine more granular stages where AI assistants are used, such as generating tests and generating docstrings, as well as less studied parts of the workflow, such as generating test data. Among the reasons for not using assistants, there are general aspects like trust and company policies, as well as more concrete issues like the lack of project-size context, which can be the focus of the future research. Conclusion. The provided analysis highlights stages of software development that developers want to delegate and that are already popular for using AI assistants, which can be a good focus for features aimed to help developers right now. The main reasons for not using AI assistants can serve as a guideline for future work.
AI snapshot
Written from the paper’s full text.
TL;DR
This large-scale survey of 481 programmers examines how AI coding assistants are used across five software-development activities and their stages, plus why developers avoid them. It finds broad adoption but uneven use, with generation and summarization stages most popular and writing tests/natural-language artifacts the activities developers most want to delegate.
Key findings
- 84.2% of respondents use at least some AI assistant occasionally or regularly; most-used tools were ChatGPT (72.1%), GitHub Copilot (37.9%), JetBrains AI Assistant (28.9%), and Visual Studio IntelliCode (17.5%).
- Implementing new features was the most enjoyable activity (86% positive) but least likely to be delegated (48% negative), while writing tests and writing natural-language artifacts were least enjoyable (46% and 43% negative) and most likely to be delegated (70% and 66%).
- Popular stages included generating new code (57.4%), generating tests (60.7%), generating data/resources for tests (54.7%), generating refactored code (56.1%), and generating comments/docstrings (51.1% each); applying changes directly was less common, e.g., applying bug fixes (27.9%).
- Top reasons for not using assistants were lack of need (22.5% of 1,559 coded responses), inaccurate AI output (17.7%), lack of trust/desire for control (15.7%), and lack of context understanding (14.4%); if shortcomings were resolved, all activities had over 60% positive delegation intent, with tests and natural-language artifacts at 71% and 72%.
Methods
- A large-scale survey with 38 main questions, including 5 open-ended, covering five activities: implementing new features, writing tests, bug triaging, refactoring, and writing natural-language artifacts, plus their individual stages.
- Data collection yielded 780 responses, 547 complete; after filtering, 481 responses were analyzed. Participants came from 71 countries, used more than 30 languages, and 48.9% had more than 10 years of professional experience.
- Analysis used Spearman correlations for Likert-scale items and thematic analysis for open-ended responses, producing 147 codes and 20 themes from 1,559 coded responses.
Limitations
- Stated: generalizability may be limited because the sample came from a specific group, including a JetBrains-curated mailing list, though the authors note the sample is large and diverse in languages and software types.
- Stated: thematic analysis may have missed some themes, though two authors coded independently and reached consensus.
- Evident: the study relies on self-reported survey responses rather than observed tool usage, and the sample is skewed toward experienced, largely corporate developers, which may shape the reported perceptions and adoption patterns.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
0 of 27 cited sources checked · 0 supported · 0 flagged
- Findingown data
The reason 'Respondents want to do the work themselves, love the process, want to understand the code better or to learn, etc.' accounts for 7.3% of coded responses.
“We Respondents want to do the work themselves, love the process, want to understand the code better or to learn, etc. 7.3%”
Quote in the paperNot a substantial claim - Findingown data
There is a negative correlation between enjoyment of an activity and willingness to delegate it to an AI assistant.
“the results reveal a negative correlation between these aspects, indicating that if a person enjoys the given activity less, they are more likely to delegate it.”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [26] Murray, 2013, Likert data: what to use, parametric or non-parametric?, Int. J. Bus. Soc. Sci.
Not checked in the free run.
- Findingown data
84.2% of respondents occasionally or regularly use AI assistants.
“Overall, 84.2% of the respondents mentioned that they use at least some tool occasionally or regularly.”
- Also stated in: § 1. Introduction · plain
“We find that 84.2% of the respondents occasionally or regularly use AI assistants”
Quote in the paperSubstantial claim - Also stated in: § 1. Introduction · plain
- Findingown data
The quality of AI-generated code most positively rated is usability, with 56% of respondents agreeing or strongly agreeing.
“the quality most positively rated is usable, with 56% of respondents agreeing or strongly agreeing with it.”
Quote in the paperSubstantial claim - Findingown data
Among individual stages, generating and summarizing code are the most widely used.
“Generating and summarizing features of AI assistants are usually the most popular.”
- Also stated in: § 1. Introduction · plain
“among individual stages, generating and summarizing code are the most widely used.”
Quote in the paperSubstantial claim - Also stated in: § 1. Introduction · plain
- Findingown data
The thematic analysis resulted in 20 distinct themes representing reasons for not using AI assistants.
“Our thematic analysis resulted in 20 distinct themes.”
- Also stated in: § Calculating correlations (RQ2). · plain
“This process resulted in a total of 20 distinct themes.”
Quote in the paperNot a substantial claim - Also stated in: § Calculating correlations (RQ2). · plain
- Findingown data
18.5% of responses related to Bug triaging mentioned Lack of understanding context by AI assistant.
“18.5% of responses related to Bug triaging mentioned Lack of understanding context by AI assistant.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Generating larger textual descriptions (such as READMEs) is relatively popular for writing natural-language artifacts (40.3%).
“other artifacts-Larger textual descriptions (such as READMEs) and Commit messages-while being different from regular comments, are also relatively popular to be generated, with 40.3% and 38.7% of respondents, respectively.”
Quote in the paperNot a substantial claim - Findingown data
A crucial theme for natural artifacts is Lack of compliance with nonfunctional requirements in AI assistant's output (9.5% responses).
“A crucial theme for natural artifacts is Lack of compliance with nonfunctional requirements in AI assistant's output (9.5% responses).”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
The median time of all complete responses is 11 minutes.
“the median time of all complete responses is 11 minutes”
Quote in the paperNot a substantial claim - Findingown data
Identifying where to insert the new feature by using code comprehension is a less popular stage of implementing new features (20%).
“Among the less popular choices are Inserting the code into the codebase (25.8%) and Identifying where to insert the new feature by using code comprehension (20%)”
Quote in the paperNot a substantial claim - Findingown data
AI-generated output being inaccurate was mentioned in 28.4% of all coded responses to the question about implementing new features.
“AI-generated output being inaccurate was mentioned in 28.4% of all coded responses to the question about implementing new features.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Generating the refactored version of the code is the most popular stage of refactoring (56.1%).
“The most popular response, with 56.1% of respondents, is Generating the refactored version of the code.”
Quote in the paperNot a substantial claim - Findingown data
Time inefficiency was raised in 11.3% of answers for implementing new features.
“Another aspect important for new features is Time inefficiency, raised in 11.3% of answers for this activity.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Generating comments at specific points in the code is a popular stage of writing natural-language artifacts (51.1%).
“The two options with the highest percentage of responses -51.1%areGenerating comments at specific points in the code and Summarizing code into docstrings.”
Quote in the paperSubstantial claim - Findingown data
Chatting with AI assistant to brainstorm ideas is the most popular stage of implementing new features (57%).
“Chatting with AI assistant to brainstorm ideas, which is present as a stage in all activities, has the noticeably highest percentage in this one -57% of our respondents chose this option.”
Quote in the paperNot a substantial claim - Findingown data
Next is User's lack of trust and the desire to feel in control, with 15.7% of responses.
“Next is User's lack of trust and the desire to feel in control, with 15.7% of responses.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Exploring the APIs of unknown libraries is a popular stage of implementing new features (50.3%).
“The other two popular stages of Implementing new features are Generating the new code (57.4%) and Exploring the APIs of unknown libraries (50.3%).”
Quote in the paperNot a substantial claim - Findingown data
Summarizing the architectural description of the codebase is a common response for writing natural-language artifacts (46.8%).
“The next most common response is Summarizing the architectural description of the codebase (46.8%)”
Quote in the paperNot a substantial claim - Findingown data
For Writing tests, 32.1% of responses mentioned Lack of need for AI assistance.
“For Writing tests, as many as 32.1% responses mentioned Lack of need for AI assistance.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
For Refactoring, 21.9% of responses mentioned User's lack of trust and the desire to feel in control.
“For Refactoring, 21.9% of responses mentioned User's lack of trust and the desire to feel in control.”
Quote in the paperNot a substantial claim- Rests on an assumption: For refactoring, it is crucial for the refactored code to not alter the logic of the original code.
- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
7.8% of responses about tests highlighted that AI-generated output is not useful.
“Also, 7.8% of responses about tests highlighted that AI-generated output is not useful”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
A lot of respondents said that they did not try AI assistants for certain artifacts, especially larger ones like READMEs.
“However, a lot of respondents said that they did not try AI assistants for certain artifacts, especially larger ones like READMEs.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
The theme of User's lack of trust and desire for control is largely prevalent in responses about applying changes directly to code.
“This theme is largely prevalent in responses about applying the changes directly to code, confirming our notion from RQ2 that a lot of respondents are not comfortable with this.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
All the other three activities are also over 60% positive.
“all the other three activities are also over 60% positive”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
The second most popular theme is AI-generated output is inaccurate, highlighted by 17.7% of responses.
“The second most popular theme is AI-generated output is inaccurate, highlighted by 17.7% of responses.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Using code comprehension to explain which specific refactoring is necessary and why is a popular stage of refactoring (49.3%).
“Another very popular response is Using code comprehension to explain which specific refactoring is necessary and why, with 49.3% of respondents selecting this option.”
Quote in the paperNot a substantial claim - Findingown data
14.4% of responses highlighted the theme of Lack of understanding context by AI assistants.
“14.4% of responses highlighted the theme of Lack of understanding context by AI assistants.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Applying the bug fix to code is among the least popular responses for bug triaging (27.9%).
“Again, one can notice that Applying the bug fix to code is among the least popular responses (27.9%)”
Quote in the paperNot a substantial claim - Findingown data
4% of responses in Refactoring mention Lack of compliance with nonfunctional requirements in AI assistant's output.
“4% of responses in this activity also mention Lack of compliance with nonfunctional requirements in AI assistant's output”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Generating data and resources for tests is a popular stage of writing tests (54.7%).
“Another popular stage is Generating data and resources for tests, which was also selected by more than half of respondents -54.7%.”
Quote in the paperNot a substantial claim - Findingown data
Using code comprehension to summarize the most likely causes of the bug is a popular stage of bug triaging (43.7%).
“The two most popular stages here are Using code comprehension to summarize the most likely causes of the bug (43.7%) and Generating the code for a potential bug fix (42.4%).”
Quote in the paperNot a substantial claim - Findingown data
Generating the new code is a popular stage of implementing new features (57.4%).
“The other two popular stages of Implementing new features are Generating the new code (57.4%) and Exploring the APIs of unknown libraries (50.3%).”
Quote in the paperNot a substantial claim - Findingown data
Finding untested areas of code is the least selected stage of writing tests (32%).
“The least selected option is Finding untested areas of code, with only 32% selection rate”
Quote in the paperNot a substantial claim - Findingown data
Generating the code for a potential bug fix is a popular stage of bug triaging (42.4%).
“The two most popular stages here are Using code comprehension to summarize the most likely causes of the bug (43.7%) and Generating the code for a potential bug fix (42.4%).”
Quote in the paperNot a substantial claim - Findingown data
The most prevalent theme is Lack of need for AI assistance, mentioned in 22.5% of all responses.
“The most prevalent theme is the Lack of need for AI assistance, mentioned in 22.5% of all responses.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
29% of responses about natural-language artifacts contained the theme of Lack of need for AI assistance.
“29% of responses about natural-language artifacts contained the theme of Lack of need for AI assistance.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
The lack of understanding context by AI assistants sometimes relates to inability to analyze the full codebase or gain access to third-party code or company-specific artifacts.
“Sometimes, this relates to more technical and specific things, in particular, the inability of an AI assistant to analyze the full codebase or gain access to third-party code or company-specific artifacts.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
For bug triaging, 34.5% do not use AI assistants in any stage.
“As many as 34.5% of the respondents do not use AI assistants in any way in this activity.”
Quote in the paperNot a substantial claim - Findingown data
Inserting the code into the codebase is a less popular stage of implementing new features (25.8%).
“Among the less popular choices are Inserting the code into the codebase (25.8%) and Identifying where to insert the new feature by using code comprehension (20%)”
Quote in the paperNot a substantial claim - Findingown data
Applying the refactoring to code directly is more popular (38.7%) than analogous choices for implementing new features and bug triaging.
“Interestingly, though, the choice of Applying the refactoring to code directly is more popular (38.7%) than analogous choices for Implementing new features and Bug triaging.”
Quote in the paperNot a substantial claim - Findingown data
Generating tests is the most popular stage of writing tests (60.7%).
“The most popular stage is Generating tests, with as many as 60.7% of the respondents selecting it.”
Quote in the paperNot a substantial claim - Findingown data
Generating commit messages is relatively popular for writing natural-language artifacts (38.7%).
“other artifacts-Larger textual descriptions (such as READMEs) and Commit messages-while being different from regular comments, are also relatively popular to be generated, with 40.3% and 38.7% of respondents, respectively.”
Quote in the paperNot a substantial claim - Findingown data
Developers indicated Writing tests and Writing natural language artifacts as the least enjoyable activities that they would want to delegate to an AI assistant.
“Developers indicated Writing tests and Writing natural language artifacts as the least enjoyable activities that they would want to delegate to an AI assistant.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
The majority of respondents said they are likely or very likely to use AI assistants for all activities if the shortcomings were overcome.
“While many different reasons for not using assistants can be seen in Table 2, still the majority of the respondents said that they are likely or very likely to use AI assistants for all activities if the shortcomings were overcome.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
One part of the lack of understanding context is the inability of the models to consider the entire codebase of the project.
“One part of it is the inability of the models to consider the entire codebase of the project.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingown data
Company policies, NDAs, etc. issues were raised in 3.6% of responses.
“This is also important for Company policies, NDAs, etc., the issues about which were raised in 3.6% of responses.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Findingreasoning
Another aspect of the lack of understanding context is the assistant's lack of access to other sources of information, such as project-specific documentation, internal knowledge bases, issue trackers, etc.
“Another aspect of this issue is the assistant's lack of access to other sources of information, such as project-specific documentation, internal knowledge bases, issue trackers, etc.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Interpretationown data
People are less willing to use AI in stages requiring precision.
“once more highlighting that people are less willing to use AI in stages requiring precision.”
Quote in the paperNot a substantial claim - Interpretationown data
Developers prefer to manually change their code for bug fixes.
“indicating that here too developers prefer to manually change their code.”
Quote in the paperNot a substantial claim - Interpretationown data
Conversational functionality for AI assistants has situational importance.
“This indicates the situational importance of conversational functionality for AI assistants.”
Quote in the paperNot a substantial claim - Interpretationown data
Among code-related natural language artifacts, in-code comments are the ones for which people use AI assistants the most.
“Both of these responses relate to in-code comments, indicating that among code-related natural language artifacts, they are the ones for which people use AI assistants the most.”
Quote in the paperSubstantial claim - Premisecitation
The existing studies do not consider individual activities within the software development life-cycle and their specificities.
“However, the existing studies do not consider individual activities within the software development life-cycle and their specificities.”
Quote in the paperSubstantial claim0 of 3 sources checked- cites [10] 2023
Not checked in the free run.
- cites [11] Wang, 2023
Not checked in the free run.
- cites [12] Zhou, 2025, Exploring the problems, their causes and solutions of AI pair programming: a study on GitHub and Stack Overflow, Journal of Systems and Software source
Not checked in the free run.
- Study design and conductown data
The study checked for responses where the first option was selected for each question and found none.
“Additionally, we checked our results for responses where the first option is selected for each question [24].We did not find such cases.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [24] Meade, 2012, Identifying careless responses in survey data, Psychol. Methods source
Not checked in the free run.
- Interpretationown data
In principle, the respondents are open to using AI assistants if the shortcomings are addressed.
“indicating that in principle, the respondents are open to using AI assistants if the shortcomings are addressed.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Study design and conductown data
The final data consisted of 481 responses after filtering.
“Thus, the final data consisted of 481 responses.”
- Also stated in: § 1. Introduction · plain
“after careful filtering, we study 481 responses.”
Quote in the paperSubstantial claim - Also stated in: § 1. Introduction · plain
- Interpretationreasoning
Resolving accuracy issues would also affect the Time inefficiency of AI tooling usage, mentioned in 5.5% of all responses.
“Therefore, resolving accuracy issues would also affect the Time inefficiency of AI tooling usage, mentioned in 5.5% of all responses.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- Premisecitation
These two activities align with the grounded theory proposed by Barke et al., which describes two developers' interaction modes with AI assistants: acceleration (supported by code generation) and exploration (supported by code summarization).
“These two activities align with the grounded theory proposed by Barke et al. [18], which describes two developers' interaction modes with AI assistants -acceleration (supported by code generation) and exploration (supported by code summarization).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [18] Barke, 2023, Grounded Copilot: How programmers interact with code-generating models, Proc. ACM Program. Lang. source
Not checked in the free run.
- Interpretationcitation
In line with previous studies, people are cautious regarding AI-generated code being insecure.
“However, in line with previous studies [30,31,32], we see that people are cautious regarding AI-generated code being insecure.”
Quote in the paperSubstantial claim0 of 3 sources checked- cites [30] G. Sandoval, H. Pearce, T. Nys, R. Karri, S. Garg, B. Dolan-Gavitt, Lost at C: A user study on the security implications of large language model code assistants, in: 32nd USENIX Security Symposium (USENIX Security 23), 2023, pp. 2205–2222.
Not checked in the free run.
- cites [31] Asare, 2023, Is GitHub’s Copilot as bad as humans at introducing vulnerabilities in code?, Empir. Softw. Eng. source
Not checked in the free run.
- cites [32] Pearce, 2022, Asleep at the keyboard? Assessing the security of GitHub Copilot’s code contributions
Not checked in the free run.
- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
- May combine two claims. 62
- The quote only partly states this claim. 5
- Classified as probably not a substantial claim. 49
May combine two claims.
Findingown dataChatGPT (72.1%), GitHub Copilot (37.9%), JetBrains AI Assistant (28.9%), and Visual Studio IntelliCode (17.5%) are the most frequently used AI assistant tools.
“we can see ChatGPT (72.1%),GitHub Copilot (37.9%),JetBrains AI Assistant (28.9%), and Visual Studio IntelliCode (17.5%) are the most frequently used tools.”
Quote in the paperNot a substantial claimThe quote only partly states this claim.
Findingown dataWriting natural-language artifacts shows a moderately negative correlation between enjoyment and willingness to delegate (r = -.32, p < .01).
“Notably, writing natural artifacts shows a moderately negative correlation (r = -.32,p < .01).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [26] Murray, 2013, Likert data: what to use, parametric or non-parametric?, Int. J. Bus. Soc. Sci.
Not checked in the free run.
May combine two claims.
Findingown dataImplementing new features is the most popular activity for AI assistance, with 87.3% of respondents using AI in at least one of its stages.
“This means that the other 87.3% use AI in at least one of the stages of this activity, making it the most popular one for AI assistance.”
- Also stated in: § 1. Introduction · plain
“Implementing new features is the most popular activity to use assistants”
Quote in the paperSubstantial claim- Also stated in: § 1. Introduction · plain
May combine two claims.
Findingown dataRegarding alignment with non-functional requirements, 28% of respondents are positive and 45% are neutral.
“Regarding the alignment with non-functional requirements, 28% of respondents are positive, and 45% are neutral.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataThe most popular reasons for not using AI assistants are Lack of need for AI assistance, AI-generated output being inaccurate, User's lack of trust and the desire to feel in control, and Lack of understanding context by AI assistant.
“The most popular ones are Lack of need for AI assistance, AI-generated output being inaccurate, User's lack of trust and the desire to feel in control, and Lack of understanding context by AI assistant.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataThe correlation between difficulty of an activity and willingness to delegate is weak and mostly not statistically significant.
“the correlation between the difficulty of the activity and willingness to delegate is weak and mostly not statistically significant, meaning that there is no connection between these two aspects of activity for our sample.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [26] Murray, 2013, Likert data: what to use, parametric or non-parametric?, Int. J. Bus. Soc. Sci.
Not checked in the free run.
May combine two claims.
Findingown data39% of respondents agree or strongly agree that AI-generated code is accurate, while 39% neither agree nor disagree.
“39% of respondents agree or strongly agree that the code provided by AI is accurate, while 39% neither agree nor disagree with this statement.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S1 (asserted), S3 (load-bearing), S4 (based).
Findingnone givenThe reason 'Time inefficiency' accounts for 5.5% of coded responses.
“## Time inefficiency”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataThe most negative opinion about AI-generated code is about security, with 23% agreeing and 40% disagreeing to some extent.
“the most negative opinion is shared about the code being secure, with just 23% of respondents agreeing and as many as 40% of them disagreeing to some extent.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataAmong respondents who do not use AI assistants, opinions about AI-generated code are much more negative: for accuracy, 21% agree and 45% disagree; for the other three qualities, more than half disagree.
“While they are a minority, their opinion is much more negative: even for the most positive quality of accurate, only 21% of them agree, and 45% disagree, whereas for the other three qualities, more than half disagree.”
Quote in the paperSubstantial claimMay combine two claims.
Findingown dataWriting tests and writing natural-language artifacts are the least enjoyable activities and the most likely to be delegated to AI assistants.
“writing tests and writing natural language artifacts are both noticeably the least enjoyable of activities (46% negative scores for tests and 43% negative scores for artifacts), and they are the ones that the developers want to delegate the most -70% and 66%, respectively.”
- Also stated in: § 4.3. RQ2: Activities and Their Stages · plain
“Among the main activities studied, implementing new features is the most enjoyable and the least likely to be delegated to an assistant, while writing tests and writing natural-language artifacts are the most unpleasant and the most likely to be delegated.”
Quote in the paperSubstantial claim- Also stated in: § 4.3. RQ2: Activities and Their Stages · plain
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe sample consists mostly of experienced programmers, with 48.9% having more than 10 years of experience and 28.9% having more than 15.
“Our sample consists mostly of experienced programmers, with 48.9% having more than 10 years of experience and 28.9% having more than 15.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataThe majority (86.7%) identify themselves as Software developers.
“The majority (86.7%) identify themselves as Software developers, but the sample also contains some of the other major technical positions: DevOps engineers, Architects, Team leads, etc.”
Quote in the paperNot a substantial claimThe quote only partly states this claim.
Findingown dataSummarizing code into docstrings is a popular stage of writing natural-language artifacts (51.1%).
“The two options with the highest percentage of responses -51.1%areGenerating comments at specific points in the code and Summarizing code into docstrings.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S1 (asserted), S3 (load-bearing). May combine two claims.
Findingown dataThe text provided by the assistant does not sound human-like, may be bloated, verbose, not fitting the conventions of the projects, or overall not useful to the human reader.
“Respondents mentioned that the text provided by the assistant does not sound human-like, may be bloated, verbose, not fitting the conventions of the projects, or overall not useful to the human reader.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingown data74.4% of the sample are fully employed in corporations and organizations.
“74.4% of our sample are fully employed in corporations and organizations, with some more being partially employed, self-employed, or freelancing.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataFor writing natural-language artifacts, about a quarter chose None of the above, and three-quarters use AI assistants in at least one stage.
“Similarly to Writing tests and Refactoring, here also about a quarter of respondents chose None of the above, and three-quarters of them use AI assistants in at least one stage.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataSome respondents indicated that the existing tools work fine for them.
“Moreover, some of them indicated that the existing tools work fine for them.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
FindingreasoningFor writing tests, 24.7% selected None of the above, meaning three-quarters use AI assistants in this activity.
“Here, we can see that 24.7% of all participants selected the option None of the above, meaning that three-quarters use AI assistants in this activity.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S1 (asserted), S3 (load-bearing), S4 (based). The quote only partly states this claim.
Findingnone givenSecurity concerns, including worries about security and AI assistants providing unsafe code, were mentioned in 2.3% of responses.
“Respondents are worried about security, the AI assistants providing unsafe code, etc.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataSome respondents mentioned that correctly prompting the AI assistant takes longer than writing the code themselves, and some mentioned that fixing the generated code takes longer.
“Some respondents mentioned that correctly prompting the AI assistant takes longer than writing the code themselves, and some mentioned that fixing the generated code takes longer.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataThe respondents came from 71 different countries and territories from all continents.
“The respondents came from 71 different countries and territories from all the continents.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe code refactored by the AI assistant may lose readability and not adhere to the project's preferences.
“highlighting that the code refactored by the AI assistant may lose readability and not adhere to the project's preferences.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe respondents use more than 30 diverse languages, with the most popular being Python (45.5%), JavaScript (31.6%), and Java (26.4%).
“They use more than 30 diverse languages, with the most popular being Python (45.5% of respondents), JavaScript (31.6%), and Java (26.4%).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataLimitations in AI's creativity, including lack of creativity, inability to provide complex solutions, and generic code, were mentioned in 2.2% of responses.
“Limitations in AI's creativity AI assistant lacks creativity, cannot provide complex solutions, provides generic code, etc.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataFor refactoring, about a quarter chose None of the above, indicating three-quarters use AI tools in at least some stages.
“Similarly to Writing tests, for Refactoring, about a quarter of respondents chose None of the above, indicating that three-quarters of them use AI tools at least in some stages.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataWorkflow disruption was mentioned in 3.5% of responses regarding Implementing new features, with respondents not being used to utilizing assistants or mentioning that they interrupt their flow.
“Workflow disruption was mentioned in 3.5% of responses regarding Implementing new features, with respondents not being used to utilizing assistants or mentioning that they interrupt their flow.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe study received 780 responses, of which 547 were complete.
“At the end of the three weeks during which the survey remained open, we received 780 responses, of which 547 were complete.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataThe respondents develop diverse types of software, including Websites (51.1%), Utilities (36.4%), and Libraries/Frameworks (30.6%).
“They also develop diverse types of software, including Websites (51.1%),Utilities (36.4%), and Libraries / Frameworks (30.6%).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataSome respondents mentioned a broader lack of understanding by AI assistants: understanding the requirements of the task, business logic, etc.
“Some respondents, however, mentioned a broader lack of understanding: understanding the requirements of the task, business logic, etc.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataRespondents mentioned that finding and fixing non-trivial bugs requires a large context, both in terms of code and in terms of a more high-level, conceptual understanding of the program, which the AI assistants lack.
“Respondents mentioned that finding and fixing non-trivial bugs requires a large context, both in terms of code and in terms of a more high-level, conceptual understanding of the program, which the AI assistants lack.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataSome respondents do not do testing at all, and some mentioned that the existing tools work well for finding untested areas of code.
“Some respondents do not do testing at all, and some mentioned that the existing tools work well for finding untested areas of code.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataSome respondents mentioned that the AI assistant's output requires careful editing and that the errors are sometimes subtle and difficult to fix.
“Some respondents mentioned that the AI assistant's output requires careful editing and that the errors are sometimes subtle and difficult to fix.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataRespondents mentioned that generated tests are sometimes useless, rudimentary, and that assistants cannot provide complex solutions.
“Specifically, respondents mentioned that the generated tests are sometimes useless, rudimentary, and that the assistants cannot provide complex solutions.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataRespondents often mentioned not trusting AI-based tools, the results being unreliable, and their desire to maintain control over the project.
“Respondents often mentioned not trusting AI-based tools, the results being unreliable, and their desire to maintain control over the project.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataWriting tests and Writing natural-language artifacts are still the most likely to be delegated (71% and 72%, respectively).
“While Writing tests and Writing natural-language artifacts are still the most likely to be delegated (71% and 72%, respectively)”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataTakeaway 4: The top reasons why developers are not using AI assistants are the lack of need, AI-generated output being inaccurate, lack of trust, and the lack of understanding of context by the assistant.
“Takeaway 4. The top reasons why developers are not using AI assistants are the lack of need, AI-generated output being inaccurate, lack of trust, and the lack of understanding of context by the assistant.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based). The quote only partly states this claim.
Findingnone givenWorkflow disruption, including not being used to AI assistants, challenges adopting them, and feeling they break workflow, was mentioned in 2.1% of responses.
“Respondents are not used to using AI assistants, have challenges with adopting it, feel like it breaks their workflow, etc.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown data2.9% of responses about tests mentioned Limitations in AI's creativity.
“and 2.9% of responses mentioned Limitations in AI's creativity.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataFrom 481 respondents in five open-ended questions, there were 1,764 responses.
“From 481 respondents in five open-ended questions, we got 1,764 responses.”
Quote in the paperNot a substantial claimMay combine two claims.
Findingown dataRespondents' lack of need for AI assistance included not trying assistants for some stages, not thinking assistance necessary because they can do the task themselves or do not perform the task, and existing non-AI-based tools working well.
“The respondents highlighted that they did not try assistants for some stages, and sometimes directly mentioned that they do not think the assistance is necessary because they can do the task themselves or they do not perform this task at all.Moreover, sometimes, they mentioned that the existing non-AI-based tools already work well.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataInefficiency for specific tasks, including the AI assistant being incapable of carrying out some specific task, was mentioned in 1.7% of responses.
“Inefficiency for specific tasks The AI assistant is incapable of carrying out some specific task, etc. 1.7%”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataThe filtering out of outliers removed 66 responses that took 30 or more minutes.
“However, it did filter out 66 responses that took 30 or more minutes to complete, with some of them taking several hours.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [25] Zijlstra, 2007, Outlier detection in test and questionnaire data, Multivar. Behav. Res. source
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingown dataLimitations of knowledge in the AI model, including outdated models, lack of domain knowledge, and poor training for non-English languages, were mentioned in 1.9% of responses.
“Limitations of knowledge in the AI model The model in the AI assistant is outdated, lacks domain knowledge, is not trained well for non-English language, etc. 1.9%”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingnone givenThe AI-generated output inaccuracy theme relates to direct inaccuracies of AI-generated output, incorrect code, hallucinations, etc.
“This group of issues relates to direct inaccuracies of AI-generated output, incorrect code, hallucinations, etc.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown dataSome respondents use refactoring as an opportunity to understand the code better and some just enjoy this activity overall.
“Some respondents use refactoring as an opportunity to understand the code better and some just enjoy this activity overall.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataAmong the 547 complete responses, 542 came from the mailing list, indicating a strong industrial backing of the sample.
“Among these 547 responses, 542 came from the mailing list, indicating a strong industrial backing of our sample.”
Quote in the paperNot a substantial claimThe quote only partly states this claim.
Findingown data10.4% of responses mention User's desire to perform the task themselves and learn for Refactoring.
“Also, as many as 10.4% of responses mention User's desire to perform the task themselves and learn.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Findingown data3.1% of responses in Bug triaging mention Inefficiency for specific tasks, specifically that AI assistants are not capable of finding bugs or fixing them.
“Also, 3.1% of responses in Bug triaging mention Inefficiency for specific tasks, specifically mentioning that AI assistants are not capable of finding bugs or fixing them.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Findingnone givenChallenges in communicating user intentions to AI assistant, including difficulty communicating intentions, assistant inability to follow instructions, and needing to point directly to code, were mentioned in 1.0% of responses.
“Respondents find it hard to communicate their intentions to the AI assistant, the assistant cannot follow instructions, requires directly pointing it to the necessary code, etc.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingown data2.7% of responses about natural-language artifacts mention Workflow disruption.
“Finally, 2.7% of responses about this activity mention Workflow disruption”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
FindingreasoningRespondents find writing tests and writing natural language artifacts to be somewhat unpleasant and express their desire to have them automated.
“The comparison of responses to different questions allows us to conclude that respondents find these tasks to be somewhat unpleasant and express their desire to have them automated.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataThe thematic analysis revealed 20 diverse issues, with the main ones being Lack of need for AI assistance, AI-generated output being inaccurate, Lack of trust, and Lack of understanding of context by AI assistant.
“In terms of the reasons for not using AI assistants, our thematic analysis revealed 20 diverse issues, with the main ones being Lack of need for AI assistance, AI-generated output being inaccurate, Lack of trust, and Lack of understanding of context by AI assistant.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
FindingcitationUser's limited knowledge or understanding of AI assistants and their capabilities was mentioned in 10.2% of responses, and Challenges in communicating user intentions to AI assistant was mentioned in 1% of responses.
“Mentioned in 10.2% of responses, User's limited knowledge or understanding of AI assistants and their capabilities, and in 1% of responses -Challenges in communicating user intentions to AI assistant, these drawbacks may be addressed by the wider and specific knowledge-sharing activities in the community and beyond it [42,43].”
Quote in the paperNot a substantial claim0 of 2 sources checked- cites [42] L. Feng, R. Yen, Y. You, M. Fan, J. Zhao, Z. Lu, CoPrompt: Supporting prompt sharing and referring in collaborative natural language programming, in: Proceedings of the CHI Conference on Human Factors in Computing Systems, 2024, pp. 1–21. source
Not checked in the free run.
- cites [43] ACM CUI, 2024
Not checked in the free run.
- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataPeople adopted the technology in their workflows and see the code provided by AI as usable and fairly accurate.
“We see that people adopted the technology in their workflows and see the code provided by AI as usable and fairly accurate.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataLack of understanding context by AI assistants was raised in 14.4% of all responses and represents one of the most specific and concrete reasons for not using AI assistants.
“This issue was raised in 14.4% of all responses and represents one of the most specific and concrete reasons for not using AI assistants.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataRespondents use AI assistants within writing tests and natural language artifacts for generating tests, generating data and resources for tests, summarizing code into docstring, and generating comments at specific points in the code.
“Our detailed subsequent questions about individual stages highlight how specifically respondents use AI assistants within these activities: generating tests, generating data and resources for tests (e.g.inputs and outputs), summarizing code into docstring, generating comments at specific points in the code.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Classified as probably not a substantial claim. May combine two claims.
Findingnone givenThe option to chat with the assistant is especially crucial when implementing new features and is present in all the other activities as well.
“Finally, while the option to chat with the assistant is especially crucial when implementing new features, it is present in all the other activities as well.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataWithin different activities, developers tend to use assistants for generation and summarization, and employ them for finding places in the code and applying code more rarely.
“Within different activities, developers tend to use assistants for generation and summarization, and employ them for finding places in the code and applying code more rarely.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
FindingcitationLegal and ethical considerations and Security concerns regarding the use of AI assistance came up in 3.1% and 2.3% of responses, respectively.
“Moreover, Legal and ethical considerations and Security concerns regarding the use of AI assistance, which came up in 3.1% and 2.3% of responses, respectively, could be addressed via system changes [36].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [36] 2022
Not checked in the free run.
- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataRespondents use AI assistants in various activities and various stages within them, but unequally.
“Our results show that respondents use AI assistants in various activities and various stages within them, but unequally.”
Quote in the paperSubstantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
May combine two claims.
Findingown dataLimitations of knowledge in the AI model and consequent Inefficiency for specific tasks were mentioned in 1.9% and 1.7% of participants' answers, respectively.
“In this line lies also the Limitations of knowledge in the AI model and consequent Inefficiency for specific tasks, mentioned in 1.9% and 1.7% of participants' answers, respectively.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
InterpretationreasoningThere is larger trust in AI when it comes to refactoring or a less critical nature of carrying out refactoring.
“This might indicate a larger trust in AI when it comes to refactoring or a less critical nature of carrying out refactoring.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
Interpretationown dataThe explanatory features of AI assistants are important.
“again indicating the importance of the explanatory features of AI assistants.”
Quote in the paperSubstantial claimMay combine two claims.
Interpretationown dataThe field of AI assistants is dominated by just several big players and smaller ones are used more rarely.
“This demonstrates that the field of AI assistants is dominated by just several big players and smaller ones are used more rarely.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningDevelopers are still more comfortable with making important decisions and changing their code manually.
“potentially indicating that developers are still more comfortable with making important decisions and changing their code manually.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
InterpretationreasoningDevelopers assume full delegation that they do not want, but actually employ assistants for some stages.
“This can be explained by the fact that developers assume full delegation that they do not want, but actually employ assistants for some stages.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductown dataThe survey was developed and piloted with experts in survey design and five pilot runs with colleagues.
“To ensure the robustness of our survey, we consulted experts in survey design and carried out five pilot runs with our colleagues.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationown dataFor refactoring, a lot of options have a high percentage of respondents, indicating the general importance of AI assistance in this activity.
“Overall, it can be noticed that for Refactoring, a lot of options have a high percentage of respondents, indicating the general importance of AI assistance in this activity.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationown dataThe top-3 most popular choices for implementing new features represent different kinds of assistance, indicating the crucial nature of assistants' versatility.
“Interestingly, all the top-3 most popular choices represent different kinds of assistance, indicating the crucial nature of assistants' versatility.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductcitationThe study filtered out outlier response times using Tukey's fences.
“we followed an established practice of filtering out outliers, applying Tukey's fences [25].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [25] Zijlstra, 2007, Outlier detection in test and questionnaire data, Multivar. Behav. Res. source
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductcitationThe study was conducted in line with the company's ethical standards and the ICC/ESOMAR International Code.
“The study was conducted in line with the company's ethical standards, adhering to the values and guidelines outlined in the ICC/ESOMAR International Code [23].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [23] 2016
Not checked in the free run.
May combine two claims.
Interpretationown dataThe results of the study support the existing notion that the current state of affairs of using AI assistants in software development is favorable and rapidly developing.
“The results of our study support the existing notion about the current state of affairs of using AI assistants in software development as favorable and rapidly developing [12,15].”
Quote in the paperNot a substantial claim0 of 2 sources checked- cites [12] Zhou, 2025, Exploring the problems, their causes and solutions of AI pair programming: a study on GitHub and Stack Overflow, Journal of Systems and Software source
Not checked in the free run.
- cites [15] A. Ziegler, E. Kalliamvakou, X.A. Li, A. Rice, D. Rifkin, S. Simister, G. Sittampalam, E. Aftandilian, Productivity assessment of neural code completion, in: Proceedings of the 6th ACM SIGPLAN International Symposium on Machine Programming, 2022, pp. 21–29. source
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductcitationThe study used the Spearman correlation coefficient for Likert-scale values, as recommended.
“For all correlations, we used the Spearman correlation coefficient, which is recommended to be used for Likert scales [26].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [26] Murray, 2013, Likert data: what to use, parametric or non-parametric?, Int. J. Bus. Soc. Sci.
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductcitationThe open-ended responses were independently coded by the first two authors, who then discussed until consensus.
“The first two authors independently read all the responses and independently coded them.Then, the two authors discussed their codes until they reached a consensus for each response using a negotiated agreement approach [28].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [28] Forman, 2007, Qualitative content analysis
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductcitationThe codes were merged into themes independently by the same two authors, then discussed until consensus.
“This task was performed independently by the same first two authors.Following the established methodology [29], both authors iteratively merged similar codes into themes.Then, the authors discussed their themes and the position of each code within them until they reached a consensus.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [29] Braun, 2006, Using thematic analysis in psychology, Qual. Res. Psychol. source
Not checked in the free run.
Probably not a substantial claim: may not pass S4 (based).
PremisereasoningTo the best of the authors' knowledge, no study has yet been conducted on a comprehensive yet granular analysis of AI assistant usage across the full software development lifecycle and its detailed steps.
“To the best of our knowledge, no study has yet been conducted on such an analysis.”
Quote in the paperNot a substantial claimMay combine two claims.
Interpretationown dataIncorrect code and hallucinations are especially critical for implementing new features, so people encountering them are cautious in using AI for this activity.
“Here, incorrect code and hallucinations are especially critical, therefore, people encountering them are cautious in using AI for this activity.”
Quote in the paperNot a substantial claim- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Probably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationThe five broad activities (implementing new features, writing tests, bug triaging, refactoring, writing natural language artifacts) correspond to large divisions of software activity in research and practice.
“The remaining survey is divided into five parts that correspond to five large divisions of software activity in research and in practice [22], which includes (1) implementing new features, (2) writing tests, (3) bug triaging, (4) refactoring, and (5) writing natural language artifacts.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [22] Lehman, 1980, Programs, life cycles, and laws of software evolution, Proc. IEEE source
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductnone givenIt is possible that our thematic analysis resulted in missing some themes, which could influence our analysis.
“It is possible that our thematic analysis resulted in missing some themes, which could influence our analysis.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductown dataOur results are based on a specific sample of people and might not generalize.
“Our results are based on a specific sample of people and might not generalize.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Study design and conductnone givenThe mailing list curated by JetBrains includes users of different IDEs and AI assistants, but it can introduce some bias into the results.
“In particular, even though the mailing list curated by JetBrains includes users of different IDEs and AI assistants, it can introduce some bias into the results.”
Quote in the paperNot a substantial claim- Rests on an assumption: The mailing list curated by JetBrains includes users of different IDEs and AI assistants.
May combine two claims.
PremisecitationPrevious research shows that developers spend almost 50% of coding time in interaction with the LLM, with 35% dedicated to double-checking suggestions, since the generated code is limited in meeting both functional and non-functional requirements.
“Previous research shows that developers spend almost 50% of coding time in interaction with the LLM, with 35% dedicated to double-checking suggestions, since the generated code is limited in meeting both functional and non-functional requirements [17].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [17] H. Mozannar, G. Bansal, A. Fourney, E. Horvitz, Reading between the lines: Modeling user behavior and costs in AI-assisted programming, in: Proceedings of the CHI Conference on Human Factors in Computing Systems, 2024, pp. 1–16. source
Not checked in the free run.
May combine two claims.
InterpretationcitationAddressing AI-generated output being inaccurate and Lack of compliance with non-functional requirements is crucial, with 17.7% and 3.2% of all responses mentioning these issues, respectively.
“Addressing AI-generated output being inaccurate and the Lack of compliance with non-functional requirements is crucial, with 17.7% and 3.2% of all responses mentioning these issues, respectively, which is in line with the study of Liang et al. [12].”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [12] Zhou, 2025, Exploring the problems, their causes and solutions of AI pair programming: a study on GitHub and Stack Overflow, Journal of Systems and Software source
Not checked in the free run.
- Rests on an assumption: The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
Classified as probably not a substantial claim. May combine two claims.
InterpretationcitationAmong the most promising steps in Implementing new features, Bug triaging and Refactoring are the generation of new necessary code and the summarization of code for a better understanding of the context of the change.
“In this regard, among the most promising steps in Implementing new features, Bug triaging and Refactoring are (a) the generation of the new necessary code and (b) the summarization of code for a better understanding of the context of the change.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim. May combine two claims.
Interpretationown dataThe high-level comparison of activities indicates that writing tests and writing natural language artifacts are good candidates for improvement.
“Our high-level comparison of activities (Section 4.3) indicates that in terms of activities, writing tests and writing natural language artifacts are good candidates for improvement.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim. May combine two claims.
Study design and conductcitationTo combat missing themes, two authors came up with codes and themes independently and then reached an agreement in the discussion, and responses that did not clearly formulate their issues were removed from the analysis.
“To combat this, we carefully followed established practices [27]: two authors came up with codes and themes independently and then reached an agreement in the discussion, and we also removed from the analysis responses that did not clearly formulate their issues.”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [27] Fereday, 2006, Demonstrating rigor using thematic analysis: A hybrid approach of inductive and deductive coding and theme development, Int. J. Qual. Methods source
Not checked in the free run.
May combine two claims.
Study design and conductcitationOur sample of 481 people is large for studies in our field and is diverse in terms of programming languages and types of developed software.
“At the same time, our sample of 481 people is large for studies in our field [47], and it is diverse in terms of programming languages and types of developed software.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites [47] Medeiros, 2017, Discipline matters: Refactoring of preprocessor directives in the #ifdef hell, IEEE Trans. Softw. Eng. source
Not checked in the free run.
The paper relies on this without support.
For refactoring, it is crucial for the refactored code to not alter the logic of the original code.
“This is important for refactoring because it is crucial for the refactored code to not alter the logic of the original code.”
The paper relies on this without support.
The respondents' self-reported reasons for not using AI assistants accurately reflect their actual reasons.
“The most prevalent theme is the Lack of need for AI assistance, mentioned in 22.5% of all responses.”
The paper relies on this without support.
The mailing list curated by JetBrains includes users of different IDEs and AI assistants.
“even though the mailing list curated by JetBrains includes users of different IDEs and AI assistants, it can introduce some bias into the results.”
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?
Understanding developers' mental models can lead to developing IDEs that align with user requirements, foster user satisfaction, and improve coding productivity while promoting their adoption.
“Understanding developers' mental models can thus lead to developing an IDEs that aligns with user requirements, fosters user satisfaction, and improves coding productivity while promoting their adoption (Sergeyuk et al., 2025).”
From Understanding user mental models in AI-driven code completion tools: Insights from an elicitation study (2025) · cites this paper as Sergeyuk et al., 2025
Section 5.1 recommends integrating features developers need into IDEs, and Section 5.2 recommends better workflow integration and UI/UX for AI coding assistants. The paper does not establish that understanding developers’ mental models leads to greater satisfaction, coding productivity, or adoption, nor does it make that claim about IDE design generally. Page numbers were not available in our copy. (LLM, conf=0.85)
Experimental — accuracy not yet measuredDevelopers need finer-grained suggestions and trustworthy explanations, which are typically not provided in CCTs.
“Other evidence about the misalignment between developers' mental models and CCTs regards the developers' need for finer-grained suggestions and trustworthy explanations (Sergeyuk et al., 2025; Wang et al., 2023), typically not provided in CCTs, as well as the different preferences about inline and sidebar layouts (Vaithilingam et al., 2023; M˘ ar˘ as , oiu et al., 2015).”
From Understanding user mental models in AI-driven code completion tools: Insights from an elicitation study (2025) · cites this paper as Sergeyuk et al., 2025
The General themes section reports developers’ lack of trust in AI assistants, and Related Work reports a proposal to add code explanations to Copilot. Section 5.1 also identifies specific kinds of assistance developers may find useful. The paper does not establish a need for finer-grained suggestions or say that trustworthy explanations are typically absent from coding tools. (LLM, conf=0.78)
Experimental — accuracy not yet measuredSuch modalities can improve usability by adapting to different workflows and developer preferences and might reduce errors due to wrong intention communication.
“Such modalities can improve usability by adapting to different workflows and developer preferences and might reduce the errors due to wrong intention communication as multiple choices may be provided when needed (Sergeyuk et al., 2025).”
From Understanding user mental models in AI-driven code completion tools: Insights from an elicitation study (2025) · cites this paper as Sergeyuk et al., 2025
Section 5.2 (page not available in our copy) recommends better integration with developers’ workflows and improved UI/UX; the section on communicating user intentions reports that developers sometimes struggle to convey what they want. The paper does not say that offering multiple modalities or choices reduces errors caused by miscommunicated intentions. (LLM, conf=0.82)
Experimental — accuracy not yet measuredGenAI coding assistants have demonstrated considerable potential to enhance developer productivity.
“GenAI coding assistants have demonstrated considerable potential to enhance developer productivity.”
From The Effects of GitHub Copilot on Computing Students' Programming Effectiveness, Efficiency, and Processes in Brownfield Coding Tasks (2025) · cites this paper as [35]
The understanding of the cognitive and interaction dynamics that developers face upon adopting CCTs is limited.
“Although some studies explored coders' expectations when dealing with CCTs (Sergeyuk et al., 2025; Wang et al., 2023), the understanding of the cognitive and interaction dynamics that developers face upon adopting CCTs is limited.”
From Understanding user mental models in AI-driven code completion tools: Insights from an elicitation study (2025) · cites this paper as Sergeyuk et al., 2025
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
Wrong figure cited for activity easiness
MinorThe discussion points to Figure 2 for opinions about how easy the activities are, but the paper identifies Figure 2 as opinions about AI-generated code. Figure 3 is the figure identified as showing opinions about the five activities.
“Overall, from Figure 2, it can be seen that opinions about the easiness of activities are more uniform, without as big differences as for other qualities.”
“Figure: 2 Figure 2 : Figure2: General opinions of respondents about code provided by AI assistants.NFR stands for non-functional requirements.”
Cites
Using thematic analysis in psychology
Braun, V., & Clarke, V. (2006) · Qualitative Research in Psychology · doi:10.1191/1478088706qp063oa · Cited by 194,414 · see citing works
Fereday, J., & Muir-Cochrane, E. (2006) · International Journal of Qualitative Methods · doi:10.1177/160940690600500107 · Cited by 11,829 · cited 2× · see citing works
“For questions about why the respondents do not use AI assistants, we used thematic analysis [34] to group the responses.”
MethodIdentifying careless responses in survey data.
Meade, A. W., & Craig, S. B. (2012) · Psychological Methods · doi:10.1037/a0028085 · Cited by 3,865 · see citing works
A review of applications in federated learning
Li, L., Fan, Y., Tse, M., & Lin, K.-Y. (2020) · Computers & Industrial Engineering · doi:10.1016/j.cie.2020.106854 · Cited by 1,559 · see citing works
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181 · see citing works
IEEE Symposium on Security and Privacy
(2023) · IT Professional · doi:10.1109/mitp.2023.3246667 · Cited by 1,180 · see citing works
Forman, J., & Damschroder, L. (2007) · Advances in Bioethics · doi:10.1016/s1479-3709(07)11003-7 · Cited by 808 · see citing works
Asleep at the Keyboard? Assessing the Security of GitHub Copilot’s Code Contributions
Pearce, H., Ahmad, B., Tan, B., Dolan-Gavitt, B., & Karri, R. (2022) · 2022 IEEE Symposium on Security and Privacy (SP) · doi:10.1109/sp46214.2022.9833571 · Cited by 476 · see citing works
Grounded Copilot: How Programmers Interact with Code-Generating Models
Barke, S., James, M. B., & Polikarpova, N. (2023) · Proceedings of the ACM on Programming Languages · doi:10.1145/3586030 · Cited by 436 · see citing works
Ross, S., Martinez, F., Houde, S., Muller, M. J., & Weisz, J. D. (2023) · ACM International Conference on Intelligent User Interfaces (IUI) · doi:10.1145/3581641.3584037 · Cited by 272 · see citing works
Empirical Methods for Bioethics: A Primer
Jacoby, L. H. (2007) · Advances in bioethics · doi:10.1016/s1479-3709(2007)11 · Cited by 214 · see citing works
A Large-Scale Survey on the Usability of AI Programming Assistants: Successes and Challenges
Liang, J. T., Yang, C., & Myers, B. A. (2024) · Proceedings of the IEEE/ACM 46th International Conference on Software Engineering · doi:10.1145/3597503.3608128 · Cited by 203 · see citing works
Productivity Assessment of Neural Code Completion
Ziegler, A., Kalliamvakou, E., Li, X. A., Rice, A., Rifkin, D., Simister, S., Sittampalam, G., & Aftandilian, E. (2022) · Proceedings of the 6th ACM SIGPLAN International Symposium on Machine Programming · doi:10.1145/3520312.3534864 · Cited by 200 · see citing works
Productivity Assessment of Neural Code Completion
Ziegler, A., Kalliamvakou, E., Simister, S., Sittampalam, G., Li, A., Rice, A., Rifkin, D., & Aftandilian, E. (2022) · arXiv · doi:10.48550/arxiv.2205.06537 · Cited by 200 · see citing works
Challenges and Applications of Large Language Models
Kaddour, J., Harris, J., Mozes, M., Bradley, H., Raileanu, R., & McHardy, R. (2023) · arXiv · doi:10.48550/arxiv.2307.10169 · Cited by 196 · see citing works
Likert Data: What to Use, Parametric or Non-Parametric?
Murray, J. (2013) · Cited by 155 · see citing works
Trust in Generative AI among Students: An exploratory study
Amoozadeh, M., Daniels, D., Nam, D., Kumar, A., Chen, S., Hilton, M., Srinivasa Ragavan, S., & Alipour, M. A. (2024) · Proceedings of the 55th ACM Technical Symposium on Computer Science Education V. 1 · doi:10.1145/3626252.3630842 · Cited by 143 · see citing works
Is GitHub’s Copilot as bad as humans at introducing vulnerabilities in code?
Asare, O., Nagappan, M., & Asokan, N. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10380-1 · Cited by 128 · see citing works
Reading Between the Lines: Modeling User Behavior and Costs in AI-Assisted Programming
Mozannar, H., Bansal, G., Fourney, A., & Horvitz, E. (2024) · Proceedings of the CHI Conference on Human Factors in Computing Systems · doi:10.1145/3613904.3641936 · Cited by 114 · see citing works
Reading Between the Lines: Modeling User Behavior and Costs in AI-Assisted Programming
Mozannar, H., Bansal, G., Fourney, A., & Horvitz, E. (2022) · arXiv · doi:10.48550/arxiv.2210.14306 · Cited by 114 · cited 1× · see citing works
“Previous research shows that developers spend almost 50% of coding time in interaction with the LLM, with 35% dedicated to double-checking suggestions, since the generated code is limited in meeting both functional and non-functional requirements [20].”
BackgroundDiscipline Matters: Refactoring of Preprocessor Directives in the #ifdef Hell
Medeiros, F., Ribeiro, M., Gheyi, R., Apel, S., Kästner, C., Ferreira, B. G., Carvalho, L. C. D. S., & Fonseca, B. (2017) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2017.2688333 · Cited by 68 · see citing works
Outlier Detection in Test and Questionnaire Data
Zijlstra, W. P., van der Ark, L. A., & Sijtsma, K. (2007) · Multivariate Behavioral Research · doi:10.1080/00273170701384340 · Cited by 59 · see citing works
Chen, J., Lu, X., Du, Y., Rejtig, M., Bagley, R., Horn, M., & Wilensky, U. J. (2024) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3613904.3642377 · Cited by 55 · see citing works
Designing PairBuddy—A Conversational Agent for Pair Programming
Robe, P., & Kuttal, S. K. (2022) · ACM Transactions on Computer-Human Interaction · doi:10.1145/3498326 · Cited by 46 · see citing works
How Practitioners Expect Code Completion?
Wang, C., Hu, J., Gao, C., Yu, J., Xie, T., Huang, H., Lei, Z., & Deng, Y. (2023) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3611643.3616280 · Cited by 42 · see citing works
Exploring the Learnability of Program Synthesizers by Novice Programmers
Jayagopal, D., Lubin, J., & Chasins, S. E. (2022) · Proceedings of the 35th Annual ACM Symposium on User Interface Software and Technology · doi:10.1145/3526113.3545659 · Cited by 40 · see citing works
Zhou, X., Liang, P., Zhang, B., Li, Z., Ahmad, A., Shahin, M., & Waseem, M. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112204 · Cited by 30 · see citing works
CoPrompt: Supporting Prompt Sharing and Referring in Collaborative Natural Language Programming
Feng, L., Yen, R., You, Y., Fan, M., Zhao, J., & Lu, Z. (2024) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3613904.3642212 · Cited by 29 · see citing works
Vaithilingam, P., Glassman, E. L., Groenwegen, P., Gulwani, S., Henley, A. Z., Malpani, R., Pugh, D., Radhakrishna, A., Soares, G., Wang, J., et al. (2023) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip58684.2023.00022 · Cited by 25 · see citing works
When to Show a Suggestion? Integrating Human Feedback in AI-Assisted Programming
Mozannar, H., Bansal, G., Fourney, A., & Horvitz, E. (2024) · Proceedings of the AAAI Conference on Artificial Intelligence · doi:10.1609/aaai.v38i9.28878 · Cited by 23 · see citing works
Grounded Copilot: How Programmers Interact with Code-Generating Models
Barke, S., James, M. B., & Polikarpova, N. (2022) · arXiv · doi:10.48550/arxiv.2206.15000 · Cited by 23 · see citing works
When to Show a Suggestion? Integrating Human Feedback in AI-Assisted Programming
Mozannar, H., Bansal, G., Fourney, A., & Horvitz, E. (2023) · arXiv · doi:10.48550/arxiv.2306.04930 · Cited by 22 · cited 1× · see citing works
“…(raised in 3% of all responses) and Workflow disruption (raised in 2.1% of responses) should be addressed by companies who provide AI assistants for the market, considering their hands-on access to the systems and their users for more quick and meaningful research and innovation [45], [46].”
BackgroundInfluentialDeepCode AI Fix: Fixing Security Vulnerabilities with Large Language ModelsPreprint
Berabi, B., Gronskiy, A., Raychev, V., Sivanrupan, G., Chibotaru, V., & Vechev, M. (2024) · arXiv (Cornell University) · doi:10.48550/arxiv.2402.13291 · Cited by 21 · see citing works
Lin, J., Bryan, B. A., Zhou, X., Lin, P., Xuan, H., Gao, L., Gu, X., Liu, Z., Wang, L.-W., Tong, S., et al. (2023) · Figshare · doi:10.6084/m9.figshare.21532908 · Cited by 3 · see citing works
"It's Weird That it Knows What I Want": Usability and Interactions with Copilot for Novice Programmers
Prather, J., Reeves, B. N., Denny, P., Becker, B. A., Leinonen, J., Luxton-Reilly, A., Powell, G., Finnie-Ansley, J., & Santos, E. A. (2023) · arXiv
Flagged first, then by citations
Research works printed but not linked: 3
- Pothukuchi, 2023, Impact of generative AI on the software development lifecycle (SDLC), Int. J. Creat. Res. Thoughts, 11
- G. Sandoval, H. Pearce, T. Nys, R. Karri, S. Garg, B. Dolan-Gavitt, Lost at C: A user study on the security implications of large language model code assistants, in: 32nd USENIX Security Symposium (USENIX Security 23), 2023, pp. 2205–2222.
- ACM CUI, 2024
Cited by
Sorted by citations
Cui, Y., & Hai, Z. (2025) · Education and Information Technologies · doi:10.1007/s10639-025-13448-1 · Cited by 36 · see citing works
Shihab, M. I. H., Hundhausen, C., Tariq, A., Haque, S., Qiao, Y., & Mulanda, B. W. (2025) · Proceedings of the 2025 ACM Conference on International Computing Education Research V.1 · doi:10.1145/3702652.3744219 · Cited by 28 · see citing works
“Beyond speed enhancements, these tools have shown capabilities in automating routine tasks like code completion, documentation generation, and test case creation [35].”
Challenges and Paths Towards AI for Software EngineeringPreprint
Gu, A., Jain, N., Li, W., Shetty, M., Shao, Y., Li, Z., Yang, D., Ellis, K., Sen, K., & Solar-Lezama, A. (2025) · Qeios · doi:10.32388/vv1661 · Cited by 24 · see citing works
How Much Does AI Impact Development Speed? an Enterprise-Based Randomized Controlled Trial
Paradis, E., Grey, K., Madison, Q., Nam, D., Macvean, A., Meimand, V., Zhang, N., Ferrari-Church, B., & Chandra, S. (2025) · 2025 IEEE/ACM 47th International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip66354.2025.00060 · Cited by 20 · see citing works
“…work that balances the sometimes-contradictory incentives to move fast and guarantee high-quality code will ensure the long-term success of AI in the developer space, especially if such work focuses on where developers might optimally trust AI and therefore want to delegate more work [25], [57].”
Do Prompt Patterns Affect Code Quality? A First Empirical Assessment of ChatGPT-Generated Code
Porta, A. D., Lambiase, S., & Palomba, F. (2025) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3756681.3756938 · Cited by 19 · see citing works
Dear Diary: A Randomized Controlled Trial of Generative AI Coding Tools in the Workplace
Butler, J., Suh, J., Haniyur, S., & Hadley, C. (2025) · 2025 IEEE/ACM 47th International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip66354.2025.00034 · Cited by 12 · see citing works
Kudriavtseva, A., Hotak, N. A., & Gadyatskaya, O. (2025) · Proceedings of the 40th ACM/SIGAPP Symposium on Applied Computing · doi:10.1145/3672608.3707778 · Cited by 9 · see citing works
"My productivity is boosted, but …" Demystifying Users’ Perception on AI Coding Assistants
Lyu, Y., Yang, Z., Shi, J., Chang, J., Liu, Y., & Lo, D. (2025) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase63991.2025.00024 · Cited by 9 · see citing works
Students' Perception of ChatGPT in Software Engineering: Lessons Learned from Five Courses
Baresi, L., Lucia, A. D., Marco, A. D., Penta, M. D., Ruscio, D. D., Mariani, L., Micucci, D., Palomba, F., Rossi, M. T., & Zampetti, F. (2025) · IEEE International Conference on Software Engineering Education and Training (CSEE&T) · doi:10.1109/cseet66350.2025.00023 · Cited by 8 · see citing works
DeutschGPT – Deutschunterricht im Dialog mit Künstlicher Intelligenz
Müller, H.-G., & Fürstenberg, M. (2025) · Frank & Timme eBooks · doi:10.26530/20.500.12657/104475 · Cited by 8 · see citing works
Chen, N., Qiu, L. K., Wang, A. Z., Wang, Z., & Yang, Y. (2026) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3772318.3790726 · Cited by 8 · see citing works
Meske, C., Hermanns, T., Weiden, E. V. D., Loser, K., & Berger, T. (2025) · SSRN Electronic Journal · doi:10.2139/ssrn.5378201 · Cited by 8 · see citing works
Desolda, G., Esposito, A., Greco, F., Tucci, C., Buono, P., & Piccinno, A. (2025) · International Journal of Human-Computer Studies · doi:10.1016/j.ijhcs.2025.103648 · Cited by 7 · see citing works
Empirical analysis of generative AI tool adoption in software development
Shao, D. D., & Ishengoma, F. (2026) · Information and Software Technology · doi:10.1016/j.infsof.2026.108036 · Cited by 7 · see citing works
Generative AI and cybersecurity: Exploring opportunities and threats at their intersection
Orpak, K. (2025) · Maandblad Voor Accountancy en Bedrijfseconomie · doi:10.5117/mab.99.149299 · Cited by 6 · see citing works
Banitaan, S., Daoud, M., Alquran, H., & Akour, M. A. (2026) · Information · doi:10.3390/info17010073 · Cited by 5 · see citing works
Robredo, M., Esposito, M., Palomba, F., Peñaloza, R., & Lenarduzzi, V. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3799717 · Cited by 5 · see citing works
Configuring Agentic AI Coding Tools: An Exploratory Study
Galster, M., Mohsenimofidi, S., Lulla, J. L., Auwal, A. M., Treude, C., & Baltes, S. (2026) · ACM International Conference on AI-Powered Software (AIware) · doi:10.1145/3805760.3814887 · Cited by 5 · see citing works
Studying How Configurations Impact Code Generation in LLMs: The Case of ChatGPT
Donato, B., Mariani, L., Micucci, D., & Riganelli, O. (2025) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/icpc66645.2025.00055 · Cited by 5 · see citing works
Comparative Analysis of ChatGPT, DeepSeek, and Gemini for Automated Code Generation
Shahzad, K., & Iqbal, S. (2025) · International Conference on Engineering of Modern Electric Systems · doi:10.1109/emes65692.2025.11045587 · Cited by 5 · see citing works
Tracking the Moving Target: A Framework for Continuous Evaluation of LLM Test Generation in Industry
Azanza, M., Lamancha, B. P., & Pizarro, E. (2025) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/3756681.3756946 · Cited by 5 · see citing works
Generative AI at the Crossroads: Light Bulb, Dynamo, or Microscope?
Baily, M. N., Byrne, D. M., Kane, A. T., & Soto, P. E. (2025) · Finance and Economics Discussion Series · doi:10.17016/feds.2025.053 · Cited by 4 · see citing works
Li, R., Liang, P., Wang, Y., Cai, Y., Sun, W., & Li, Z. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3798163 · Cited by 4 · see citing works
Architecting open, accountable, and trustworthy AI-IDEs
Contreras, A., Guerra, E., & de Lara, J. (2026) · Automated Software Engineering · doi:10.1007/s10515-026-00608-x · Cited by 4 · see citing works
Human-Agent versus Human Pull Requests: A Testing-Focused Characterization and Comparison
Milanese, R., Salzano, F., Spina, A., Vitale, A., Pareschi, R., Fasano, F., & Fazzini, M. (2026) · International Conference on Mining Software Repositories (MSR) · doi:10.1145/3793302.3793617 · Cited by 4 · see citing works
Advancing research software engineering with AI: a research framework
Farshidi, S., Bennin, K. E., Babur, Ö., Sallou, J., Kassahun, A., & Teki̇nerdoğan, B. (2026) · Automated Software Engineering · doi:10.1007/s10515-026-00621-0 · Cited by 3 · see citing works
Starace, L. L. L. (2026) · Journal of Systems and Software · doi:10.1016/j.jss.2026.112989 · Cited by 3 · see citing works
Towards Personalized and Contextualized Code Explanations
Brachman, M., Goldberg, A., Anderson, A. W., Houde, S., Muller, M. J., & Weisz, J. D. (2025) · ACM Conference on User Modeling, Adaptation and Personalization (UMAP) · doi:10.1145/3708319.3733681 · Cited by 3 · see citing works
Stalnaker, T., Wintersgill, N., Chaparro, O., Heymann, L. A., Tufo, M., Germán, D. M., & Poshyvanyk, D. (2025) · SSRN Electronic Journal · doi:10.2139/ssrn.5353252 · Cited by 3 · see citing works
Esnaola, L. M., Ramón, H. D., & Lanzarini, L. C. (2026) · Empirical Software Engineering · doi:10.1007/s10664-026-10813-7 · Cited by 2 · see citing works
Exploring the Challenges and Opportunities of AI-assisted Codebase Generation
Eibl, P., Sabouri, S., & Chattopadhyay, S. (2025) · IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl-hcc65237.2025.00034 · Cited by 2 · see citing works
Developers and generative AI: A study of self-admitted usage in open source projects
Tufano, R., Pepe, F., Zampetti, F., Mastropaolo, A., Dabić, O., Penta, M. D., & Bavota, G. (2026) · Empirical Software Engineering · doi:10.1007/s10664-026-10848-w · Cited by 2 · see citing works
When Help Hurts: Verification Load and Fatigue with AI Coding Assistants
Fan, G. F., Liu, D., Pan, L., & Zhang, R. (2026) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3772318.3791176 · Cited by 2 · see citing works
Pitfalls and risks of generative AI in machine learning
Lones, M. A. (2026) · Patterns · doi:10.1016/j.patter.2026.101534 · Cited by 2 · see citing works
Janabi, I. A., & Bland, T. (2026) · AI · doi:10.3390/ai7060223 · Cited by 2 · see citing works
Shameem, M., Anwer, S., Mahmood, S., Algamdi, S. A., Niazi, M., & Mohammed, M. (2026) · Applied Soft Computing · doi:10.1016/j.asoc.2026.116127 · Cited by 2 · see citing works
ATHENA: A customizable LLM-based Code Completion Tool for Visual Studio Code
Desolda, G., Esposito, A., Greco, F., Tucci, C., Buono, P., & Piccinno, A. (2025) · ACM International Conference on Intelligent User Interfaces (IUI) · doi:10.1145/3708557.3716357 · Cited by 2 · see citing works
Coding-free virtual flowmeter for building chilled water using pump VFD data and LLM
Qiu, S., Feng, F., Zhang, X., Xu, S., & Wu, Q. (2025) · Flow Measurement and Instrumentation · doi:10.1016/j.flowmeasinst.2025.102943 · Cited by 2 · see citing works
Programming Language Confusion: When Code LLMs Can't Keep Their Languages Straight
Moumoula, M. B., Nikiema, S. L., Kaboré, A. K., Klein, J., & Bissyandé, T. F. (2026) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner67736.2026.00087 · Cited by 2 · see citing works
To Ban or Not to Ban? How Open Source Projects Govern GenAI Contributions
Yang, W., He, R., & Zhou, M. (2026) · Proceedings of the 41st IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3832783.3837448 · Cited by 1 · see citing works
Exploring Persuasive Explanations to Motivate the Adoption of SOLID Principles
Pribik, I., Lubos, S., & Felfernig, A. (2026) · Communications in computer and information science · doi:10.1007/978-3-032-16448-3_6 · Cited by 1 · see citing works
Zhang, Y., Siau, K. L., & Sung, J. (2026) · Software & Systems Modeling · doi:10.1007/s10270-026-01383-9 · Cited by 1 · see citing works
Patel, P., & Melcer, E. F. (2025) · International Conference on PErvasive Technologies Related to Assistive Environments (PETRA) · doi:10.1145/3733155.3737913 · Cited by 1 · see citing works
Wan, B. (2025) · Advances in Economics Management and Political Sciences · doi:10.54254/2754-1169/2025.lh26978 · Cited by 1 · see citing works
Boosting unit test generation via structure-aware fine-tuning of pre-trained model
Qiu, S., Chen, W., Liu, H., Wang, S., & Huang, H. P. (2025) · Information and Software Technology · doi:10.1016/j.infsof.2025.107948 · Cited by 1 · see citing works
Seo, J., Deldari, E., & Mentis, H. M. (2026) · ACM International Conference on Intelligent User Interfaces (IUI) · doi:10.1145/3742413.3789121 · Cited by 1 · see citing works
Axetorn, J., Edholm, F., Dobslaw, F., & Gren, L. (2026) · Requirements Engineering · doi:10.1007/s00766-026-00457-w · Cited by 1 · see citing works
An intelligent low-code platform for building task-oriented LLM-based chatbots
Quiles, Á., Guerra, E., & de Lara, J. (2026) · Journal of Computer Languages · doi:10.1016/j.cola.2026.101401 · Cited by 1 · see citing works
An Automated Methodology for Generating Labeled Datasets of Semantic Errors in Code
Kassem, M., Ribeiro, F., & Nadi, S. (2026) · International Workshop on Large Language Models for Code (LLM4Code) · doi:10.1145/3786181.3788730 · Cited by 1 · see citing works
Fein, B., Fraser, G., & Herbold, S. (2026) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3786580.3786962 · Cited by 1 · see citing works
Generative AI and the Future of Professional Software Development: Survey Findings from Finland
Määttä, S., Kelanti, M., & Turhan, B. (2026) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3803437.3805619 · Cited by 1 · see citing works
Learning to Code with Context: A Study-Based Approach
Borghoff, U. M., Minas, M., & Schopp, J. (2026) · Software · doi:10.3390/software5020027
“This task-oriented interpretation is consistent with recent findings showing that developers use AI-based coding assistants unevenly across software development activities and stages [49].”
Torres, J. C. G., Lacorte, A. M., & Calvez, J. P. G. (2026) · 2026 12th International Conference on Education and Training Technologies (ICETT) · doi:10.1109/icett70124.2026.11666173
Розробка AI асистента для локального користувача на мові програмування Python
Pronina, O. I., & Синицін, Р. В. (2025) · COMPUTER-INTEGRATED TECHNOLOGIES EDUCATION SCIENCE PRODUCTION · doi:10.36910/6775-2524-0560-2025-58-15
Pizarro, E., Azanza, M., & Lamancha, B. P. (2025) · Congresso Ibero-Americano em Engenharia de Software (CIbSE) · doi:10.5753/cibse.2025.35294
Swaraj, A., Kumar, S., & Sharma, L. M. (2025) · Computer · doi:10.1109/mc.2025.3532347
The AI-Driven Vendor: Impact of AI on Offshore Software Outsourcing
Wende, E., Alt, R., & Nguyen, C. (2025) · Lecture notes in business information processing · doi:10.1007/978-3-032-04512-6_7
Designing Human-Centered Code Completion Tools in the Age of Generative AI
Desolda, G., Esposito, A., Greco, F., Tucci, C., Buono, P., & Piccinno, A. (2025) · Biannual Conference of the Italian SIGCHI Chapter (CHItaly) · doi:10.1145/3750069.3755957
Traditional Coding, Low-Code and AI Assistants
Heras, F. (2025) · Communications in computer and information science · doi:10.1007/978-3-032-08614-3_11
Bug detective and quality coach: Developers’ mental models of AI-assisted IDE tools
Buono, P., Cerullo, M., Cirillo, S., Desolda, G., Greco, F., Guglielmi, E., Margarella, G., Polese, G., Scalabrino, S., & Tucci, C. (2026) · Computers in Human Behavior Reports · doi:10.1016/j.chbr.2026.101157
Simbeck, K. (2025) · Literatur - Medien - Didaktik · doi:10.57088/978-3-7329-8796-2_1
Hyun, S., Kim, H., Jang, J., Choi, H., & Babar, M. A. (2026) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3844949
Петренко, С. В. (2025) · Інфокомунікаційні та комп’ютерні технології · doi:10.36994/2788-5518-2025-01-09-04
Software Vulnerability Management in the Era of Artificial Intelligence: An Industry Perspective
Kholoosi, M. M., Le, T. H. M., & Babar, M. A. (2026) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3744916.3787781
Artificial Intelligence and Education
Filiz, O. (2025) · Advances in computational intelligence and robotics book series · doi:10.4018/979-8-3373-8857-1.ch003
Hein, D. K. (2026) · Lecture notes in business information processing · doi:10.1007/978-3-032-14518-5_12
The Expert Validation Framework (EVF): Enabling Domain Expert Control in AI Engineering
Gren, L., & Dobslaw, F. (2026) · IEEE/ACM International Conference on AI Engineering – Software Engineering for AI (CAIN) · doi:10.1145/3793653.3793796
Lumen: Developer Agency Through Transparent Context Control in AI-Assisted Programming
Goel, N., & Melo, G. (2025) · IEEE International Conference on Collaborative Advances in Software and Computing (CASCON) · doi:10.1109/cascon66301.2025.00024
APIDA-Chat: Structured Synthesis of API Search Dialogues to Bootstrap Conversational Agents
Eberhart, Z., & Collin, M. (2025) · IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase63991.2025.00382
Security and privacy challenges of AI-powered coding assistants
Ozman, F. M. (2026) · World Journal of Advanced Engineering Technology and Sciences · doi:10.30574/wjaets.2026.18.1.0056
Matejić, T., Mihailović, Đ., & Dukić, A. (2025) · Limes plus. · doi:10.69899/limes-plus25222046m
A Systematic Literature Review on Intelligent Tools and the Developer Experience
Galván, D. A. Á., Benítez–Guerrero, E., & Mezura-Godoy, C. (2025) · International Conference in Software Engineering Research and Innovation (CONISOFT) · doi:10.1109/conisoft66928.2025.00046
Aguilar-López, R., Sanchéz-García, Á. J., Pérez-Arriaga, J. C., & Limón, X. (2025) · International Conference in Software Engineering Research and Innovation (CONISOFT) · doi:10.1109/conisoft66928.2025.00047
Yu, X., Zhong, V., & Crisan, A. (2026) · ACM International Conference on Intelligent User Interfaces (IUI) · doi:10.1145/3742413.3789088
The Impact of Artificial Intelligence on Web UI Development
Bezhentsev, Y. (2026) · Universal library of engineering technology. · doi:10.70315/uloap.ulete.2026.0301010
Bug Detective and Quality Coach: Developers’ Mental Models of AI-Assisted IDE ToolsPreprint
Buono, P., Cerullo, M., Cirillo, S., Desolda, G., Greco, F., Guglielmi, E., Margarella, G., Polese, G., Scalabrino, S., & Tucci, C. (2026) · SSRN Electronic Journal · doi:10.2139/ssrn.6411746
Virtual AI assistants in the manufacturing industry – innovation diffusion perspective
Hakanen, T., Goriachev, V., & Tikka, P. (2026) · Procedia Computer Science · doi:10.1016/j.procs.2026.02.219
Bhatlawande, S. S., Deshmukh, V., Date, A., & Deshpande, P. (2025) · IEEE International Conference on Emerging Trends in Computing and Communication (ETCOM) · doi:10.1109/etcom66606.2025.11436475
Flamourtzoglou, N., Vrochidou, Ε., & Papakostas, G. A. (2025) · International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT) · doi:10.1109/3ict68299.2025.11442232
Korat, A. S. (2026) · Advances in computational intelligence and robotics book series · doi:10.4018/979-8-3373-8450-4.ch004
Muratović, A., & Tanović, A. (2026) · International Symposium INFOTEH-JAHORINA (INFOTEH) · doi:10.1109/infoteh68759.2026.11477738
Ghodke, P., Kumbhar, B., & Sadam, R. (2026) · Innovations in Software Engineering Conference (ISEC) · doi:10.1145/3796563.3796589
Белинская, И. В., & Смолякова, А. А. (2026) · Социально-гуманитарные исследования: векторы развития науки и образования · doi:10.21202/978-5-8399-0894-9_396-400
Model Context Protocol Approach to Reducing Test Development Effort in Web Automation
Cherkashyn, O. (2026) · International Journal of Scientific Research and Modern Technology. · doi:10.38124/ijsrmt.v5i6.1474
Gugushvili, A., & Lennert, F. (2026) · AI & Society · doi:10.1007/s00146-026-03136-0
Beyond the hype: Enabling informed LLM adoption in industry through systematic evaluation
Pizarro, E., Azanza, M., & Lamancha, B. P. (2026) · Science of Computer Programming · doi:10.1016/j.scico.2026.103530
Yeşilyayla, H. (2026) · Journal of Business Innovation and Governance · doi:10.54472/jobig.1921341
Analyzing the Impact of Generative AI Assistants Use in Undergraduate Programming Courses
Amer, J., Ibrahim, N., & Abu-Elkheir, M. (2026) · IEEE Global Engineering Education Conference (EDUCON) · doi:10.1109/educon67543.2026.11574431
Compiling Code LLMs into Lightweight Executables
Shi, J., He, J., Yang, Z., Yang, C., Klymenko, M. V., Hoang, T., Xu, X., Xing, Z., & Lo, D. (2026) · Proceedings of the ACM on software engineering. · doi:10.1145/3808196
Smith, C. R., Girin, N., Laberge, K., Manthey, S., Marcynuk, P., Pevzner, E. S., Roth, A., & Wong, L. (2026) · Eurosurveillance · doi:10.2807/1560-7917.es.2026.31.26.2500677
Multi-task Code LLMs: Data Mix or Model Merge?
Zhu, M., Merler, M., Sobolev, B., Krishna, R., Pavuluri, R., & Patterson, S. (2026) · International Workshop on Large Language Models for Code (LLM4Code) · doi:10.1145/3786181.3788714
Zhao, S., Wang, Z., Chen, T., Kang, C., & Lan, Y. (2026) · Educational Technology Research and Development · doi:10.1007/s11423-026-10663-6
Hope or Hype? Understanding Vibe Coding through Software Practitioner Discussions
Meem, F. N., Zohra, F. T., Smith, J., & Johnson, B. (2026) · International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE) · doi:10.1145/3794860.3794904
AI-Powered Code Generation in Agile Workflows: Risks, Review Strategies, and Developer Perceptions
Amanbayev, M., Aukatov, S., Nagumanov, A., Сахипов, А., Nurgaliyeva, S., & Омирзак, И. (2026) · IEEE International Conference on Smart Information Systems and Technologies (SIST) · doi:10.1109/sist61674.2026.11596025
CoRenameAgent: A Human-In-The-Loop, Multi-Agent Tool for Coordinated Rename Refactoring
Bellur, A., Ullah, M. R., Batole, F., Kansara, M., Morimoto, M., Ishikawa, K., Chen, H., Klause, H., Zharov, Y., Bryksin, T., et al. (2026) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3803437.3806418
Self-citationAI in Formal IDEs: Improving Usability or Undermining Trust?
Moreira, E. J. V. F., & Campos, J. C. (2026) · Lecture notes in computer science · doi:10.1007/978-3-032-22937-3_5
An Empirical Analysis of LLM-Driven Refactoring for Microservices
Köse, A. H., Yılmaz, R., & Buzluca, F. (2026) · IEEE International Conference on Software Architecture Companion (ICSA-C) · doi:10.1109/icsa-c68850.2026.00074
An, Y., & Yang, Y. (2026) · International Conference on Computer Science and Technologies in Education (CSTE) · doi:10.1109/cste69562.2026.11649809
Yao, X., Xu, F., & Shao, Y. (2026) · International Journal of Human-Computer Interaction · doi:10.1080/10447318.2026.2746841
Decision-Makers’ Perceptions of Barriers to AI Coding Assistant Adoption—A Survey Study
Rzanny, P., Ochodek, M., & Staron, M. (2026) · Lecture notes in computer science · doi:10.1007/978-3-032-36590-3_12
- Authors
- Sergeyuk, A., Golubev, Y., Bryksin, T., & Ahmed, I.
- Affiliations
- University of California, Irvine (US)
- Corresponding author
- Golubev, Yaroslav
- Venue
- Information and Software Technology
- Publisher
- Elsevier BV
- Published
- 2025-02
- Volume
- 178
- Pages
- 107610
- ISSN
- 0950-5849 (ISSN-L)
- OpenAlex
- W4403913792
- Semantic Scholar
- 16ef275e37ff5abb595da64a4a21d86cd3d637ff
- Cited by
- 101
- References
- 32
- Citations by year
- 2026: 65 · 2025: 36
- FWCI
- 38.05
- Type
- journal article
- Language
- en
- Open access
- green
- doi.org
- Licence
- Locations
- Information and Software Technology (publishedVersion)
- SSRN Electronic Journal (acceptedVersion)
- arXiv (Cornell University) (submittedVersion, cc-by-nc-nd)
- arXiv (Cornell University)
- 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 › Computer Science Applications › Open Source Software Innovations
- Keywords
- AI coding assistants, developer perceptions, software development workflow, test case generation, test data generation, bug triage, refactoring, developer trust, company policy
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.
Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-06.
Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-06.
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