AI-assisted programming tools are widely adopted, yet their practical utility is often undermined by undesired suggestions that interrupt developer workflows and cause frustration. While existing research has explored developer-AI interactions when programming qualitatively, a significant gap remains in quantitative analysis of developers’ acceptance of AI-generated code suggestions, partly because the necessary fine-grained interaction data is often proprietary. To bridge this gap, this paper conducts an empirical study using 66,239 industrial developer-AI interactions from a large technology company. We analyze features that are significantly different between accepted code suggestions and rejected ones. We find that accepted suggestions are characterized by significantly higher historical acceptance counts and ratios for both developers and projects, longer generation intervals, shorter preceding code context in the project, and older IDE versions. Based on these findings, we introduce CSAP (Code Suggestion Acceptance Prediction) to predict whether a developer will accept the code suggestion before it is displayed. Our evaluation of CSAP shows that it achieves an accuracy of 0.973 and 0.922 on the imbalanced and balanced datasets, respectively. Compared to a large language model baseline and an in-production industrial filter, CSAP improves the accuracy by 12.6% and 69.5% on the imbalanced dataset, and by 87.0% and 140.1% on the balanced dataset. Our results demonstrate that targeted personalization is a powerful approach for filtering out code suggestions with predicted rejection and reducing developer interruption. To the best of our knowledge, it is the first quantitative study of code suggestion acceptance on large-scale industrial data, and this work also sheds light on an important research direction of AI-assisted programming.
Jing Jiang, Liehao Li, Jinyu Hou et al.· Proceedings of the ACM on So...· 0 citations
The rapid advancement of LLMs has opened new opportunities in automated software engineering, driving progress in code understanding, agent-based workflows, and productivity tools. However, existing code intelligence systems have largely sidelined the end-users they aim to serve—the developers themselves. Developers exhibit substantial heterogeneity across multiple dimensions: coding style, toolchain preferences, domain-specific expertise, and problem-solving strategies. Failing to account for these individual differences directly compromises both the effectiveness of code intelligence and the likelihood of its adoption. For example, a senior architect and a junior engineer ask: "Describe the authorization module." Without personalized context, the system produces a uniform response—verbose for the expert, incomprehensible for the novice. This gap motivates a fundamental shift: from one-size-fits-all to one-size-fits-one code intelligence. A developer's dynamic in-IDE behaviors—code authoring patterns, navigation pathways, debugging trajectories—implicitly encode a rich representation of their competencies and habits. If captured and interpreted systematically, these signals can enable Personalized Code Intelligence, formalized as: [EQUATION] where P is the developer persona derived from IDE behaviors, injected alongside code context C and instruction ℐ.
Yuhong Liu, Yu Su, Zhipeng Peng et al.· SIGSOFT FSE Companion· 1 citation