paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Reading Between the Lines: Scalable User Feedback via Implicit Sentiment in Developer Prompts

从字里行间解读:基于开发者提示中隐式情感的可扩展用户反馈
ICSE Proceedings of the IEEE/ACM 48th International Conference on Software Engineering2026匹配度 1/10 · 论文聚焦通过开发者提示词的情感分析来挖掘隐式满意度信号,属于开发者体验与用户反馈研究,不涉及静态分析、形式化验证、浮点程序分析或贝叶斯程序分析,也未将 LLM/Agent 用于改进程序分析。引用 0 inbox
Daye Nam, Malgorzata Salawa, Satish Chandra
crossref: 2026-09-12

AI 速览

一句话:提出用开发者提示词的情感分析挖掘隐式满意度信号,以可扩展方式补充传统反馈渠道。

评估开发者对对话式 AI 助手的满意度在大规模下十分困难:用户研究深入但不可扩展,日志或产品内评分等定量信号又过于浅层或稀疏。本文提出并评估一种新方法:对开发者提示进行情感分析,以识别用户满意度的隐式信号。作者分析 372 名专业开发者的工业使用日志,发现该方法能在约 8% 的交互中识别出信号,频率是显式用户反馈的 13 倍以上;即使使用现成的情感分析方法,准确率也较为合理。该实践可补充现有反馈渠道,帮助大规模理解开发者体验。

问题
大规模评估开发者对对话式 AI 助手的满意度十分困难,现有用户研究不可扩展,而日志或产品内评分等定量信号往往过于浅层或稀疏。
方法
对开发者提示进行情感分析,从工业使用日志中挖掘隐式满意度信号,并与显式反馈渠道进行比较。
评估
分析 372 名专业开发者的工业使用日志,衡量隐式信号的识别覆盖率、相对显式反馈的频率,以及现成情感分析方法的准确率。
原文摘要(Abstract)

Evaluating developer satisfaction with conversational AI assistants at scale is critical but challenging. User studies provide rich insights, but are unscalable, while large-scale quantitative signals from logs or in-product ratings are often too shallow or sparse to be reliable. To address this gap, we propose and evaluate a new approach: using sentiment analysis of developer prompts to identify implicit signals of user satisfaction. With an analysis of industrial usage logs of 372 professional developers, we show that this approach can identify a signal in ~8% of all interactions, a rate more than 13 times higher than explicit user feedback, with reasonable accuracy even with an off-the-shelf sentiment analysis approach. This new practical approach to complement existing feedback channels would open up new directions for building a more comprehensive understanding of the developer experience at scale.

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot12053,
  title = {Reading Between the Lines: Scalable User Feedback via Implicit Sentiment in Developer Prompts},
  author = {Daye Nam and Malgorzata Salawa and Satish Chandra},
  booktitle = {ICSE},
  year = {2026},
  doi = {10.1145/3786582.3786801}
}