AI 中文总结
本研究通过对119名软件从业者的调查，分析了工程师使用LLMs时的依赖、过度依赖及成瘾相关行为，发现LLMs已成为软件工程的习惯性工具，多数使用具功能性，需促进适当依赖。
AI 中文摘要
大语言模型（LLMs）的广泛采用改变了软件工程师开展日常开发活动的方式。尽管这些系统为代码生成、调试、文档编写等任务提供了大量支持，但它们日益融入专业工作流程也引发了关于开发者对这些工具的依赖、以及依赖、过度依赖和成瘾相关行为出现的问题。本研究调查软件工程师在专业软件开发中使用LLMs的体验，重点关注与依赖、过度依赖及成瘾相关行为有关的行为模式。对119名软件从业者开展了探索性调查，采用描述性统计和对参与者开放式回答的定性主题分析对数据进行分析。参与者主要描述了功能性依赖，因LLMs能提升生产力和效率，已融入常规软件工程活动。回答还显示出与过度依赖一致的模式，尤其表现为在继续验证生成输出的同时，优先选择LLMs而非文档或同行咨询。与成瘾相关行为的报告较少，主要反映出难以控制使用或对该技术产生情感依恋，而非控制能力受损。研究结果表明，LLMs正成为专业软件工程实践的习惯性组成部分。尽管多数报告的使用看似具有功能性，但结果表明，在整个软件开发过程中，通过支持信任校准、专业判断和验证来促进适当依赖十分重要。
英文摘要
The widespread adoption of Large Language Models (LLMs) has changed how software engineers perform everyday development activities. While these systems provide substantial support for tasks such as code generation, debugging, and documentation, their increasing integration into professional workflows has also raised questions regarding developers' reliance on these tools and the emergence of dependence, overreliance, and addiction-related behaviors. This study investigates how software engineers experience the use of LLMs during professional software development, with attention to behavioral patterns associated with dependence, overreliance, and addiction-related behaviors. An exploratory survey was conducted with 119 software practitioners. The data were analyzed using descriptive statistics and qualitative thematic analysis of participants' open-ended responses. Participants primarily described functional dependence, with LLMs becoming integrated into routine software engineering activities because of the productivity and efficiency they provide. Responses also suggested patterns consistent with overreliance, particularly through prioritizing LLMs over documentation or peer consultation while continuing to verify generated outputs. Reports associated with addiction-related behaviors were less common and primarily reflected difficulty moderating use or emotional attachment to the technology rather than impaired control. The findings suggest that LLMs are becoming a habitual component of professional software engineering practice. While most reported use appears functional, the results indicate the importance of promoting appropriate reliance by supporting trust calibration, professional judgment, and verification throughout software development.
