一句话:首个大规模调查表明代码审查中字母排序文件与认知不匹配,开发者呼吁依赖感知和可定制的排序工具。
该研究关注代码审查工具默认按字母顺序排列 Pull Request 变更文件的做法,及其对审查者认知与效果的影响。作者对来自 182 个常用开源项目的 1,355 名职业开发者开展混合方法调查,分析文件排序如何影响审查行为、理解与感知效果。结果显示,仅 10.2% 的审查者认为字母排序最优;57.6% 的开发者表示该顺序增加上下文切换、打断逻辑推理并导致审查疲劳;63.9% 担心默认排序会使其漏掉缺陷。研究还识别了多文件审查的挑战,并发现 66% 的审查者期望依赖感知分组和可定制文件排序,强调需要以审查者为中心的界面设计。
Effective code review is central to maintaining software quality, yet there is limited research about how the ordering of changed files in Pull Requests (PRs) influences review effectiveness. Most popular code review tools default to alphabetical ordering, favoring predictability over contextual relevance. While prior studies examined how file position shapes reviewer attention, it remains unclear how such ordering influences cognitive load and perceived review thoroughness. This study presents the first large-scale survey of 1,355 professional developers across 182 widely used open-source projects to investigate how file ordering impacts review behavior, comprehension, and perceived effectiveness. Our mixed-methods analysis reveals that only 10.2% of reviewers consider alphabetical ordering optimal, underscoring a cognitive misalignment in their interpretation of code changes. Although some developers appreciate its predictability, more than half (57.6%) report that it increases context switching, disrupts logical reasoning, and contributes to review fatigue, and 63.9% expressed concern that the default ordering may cause them to miss bugs. We further identify key challenges in multi-file reviews and elicit developers’ expectations for improved tooling, including dependency-aware grouping and customizable file ordering (requested by 66% of reviewers). These findings highlight the need for reviewer-centric interface designs that better align tool behavior with human cognition.