Christian Bird
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Christian Bird has a total of 83 co-authors. Here are the top co-authors by number of shared publications:
- Thomas Zimmermann
University of California, Irvine
11 shared publications - Margaret-Anne Storey
University of Victoria, Canada
5 shared publications - Robert DeLine
Microsoft, Redmond, USA
5 shared publications - Carmen Badea
Microsoft Research, Redmond, USA
4 shared publications - Emerson Murphy-Hill
Microsoft, Mountain View, USA
4 shared publications - Jenna L. Butler
Microsoft, Redmond, WA, USA
4 shared publications
Latest Publications
- Open Access
- 1 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 197-203
The Conversation We’re Not Having about AI in Peer Review
Whether we like it or not, AI is already part of peer review. Our community has barely begun to discuss how reviewers use it or what norms should govern that use. We have independently developed AI-assisted reviewing workflows and discovered that our practices converged on similar boundaries. In this essay, we describe those workflows in detail, report what changed as a result of using AI, and reflect on what the experience revealed about our own longstanding reviewing habits. We close with an initial set of guidelines as a starting point for the community to develop explicit, shared norms for AI use in reviewing.
- 1 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 197-203
Open AccessThe Conversation We’re Not Having about AI in Peer Review
Whether we like it or not, AI is already part of peer review. Our community has barely begun to discuss how reviewers use it or what norms should govern that use. We have independently developed AI-assisted reviewing workflows and discovered that our practices converged on similar boundaries. In this essay, we describe those workflows in detail, report what changed as a result of using AI, and reflect on what the experience revealed about our own longstanding reviewing habits. We close with an initial set of guidelines as a starting point for the community to develop explicit, shared norms for AI use in reviewing.
- Top Cited PapersOpen Access
- 17 June 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 35 (7) , 1-34
Facilitating Trust in AI-assisted Software Tools
The day-to-day of a software engineer involves a variety of tasks. While many of these tasks are collaborative, it is not always possible or feasible to engage with other engineers for task completion. Software tools, such as code generators and static analysis tools, aim to fill this gap by providing additional support for developers to effectively complete their tasks. With a steady stream of new tools emerging to support software engineers, including a new breed of tools that rely on AI, there are important questions to answer regarding the trust engineers can, and should, put into their software tools and what it means to build a trustworthy tool. To this end, this article presents findings from a mixed methods investigation of the factors that contribute to trust in traditional and AI-assisted software tools. First, we introduce the PICSE (pronounced “pixie”) framework for trust in software tools that we developed based on a set of 18 interviews with software practitioners internal and external to Microsoft. We then discuss insights from a survey with 368 internal Microsoft responses on the relevance and importance of the factors in our framework with respect to traditional and AI-assisted tools.
- 17 June 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 35 (7) , 1-34
Top Cited PapersOpen AccessFacilitating Trust in AI-assisted Software Tools
The day-to-day of a software engineer involves a variety of tasks. While many of these tasks are collaborative, it is not always possible or feasible to engage with other engineers for task completion. Software tools, such as code generators and static analysis tools, aim to fill this gap by providing additional support for developers to effectively complete their tasks. With a steady stream of new tools emerging to support software engineers, including a new breed of tools that rely on AI, there are important questions to answer regarding the trust engineers can, and should, put into their software tools and what it means to build a trustworthy tool. To this end, this article presents findings from a mixed methods investigation of the factors that contribute to trust in traditional and AI-assisted software tools. First, we introduce the PICSE (pronounced “pixie”) framework for trust in software tools that we developed based on a set of 18 interviews with software practitioners internal and external to Microsoft. We then discuss insights from a survey with 368 internal Microsoft responses on the relevance and importance of the factors in our framework with respect to traditional and AI-assisted tools.
- Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 2582-2595
"Maybe We Need Some More Examples:" Individual and Team Drivers of Developer GenAI Tool Use
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 2582-2595
Open Access"Maybe We Need Some More Examples:" Individual and Team Drivers of Developer GenAI Tool Use
- Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 428-439
AI Where It Matters: Where, Why, and How Developers Want AI Support in Daily Work
Generative AI is reshaping software work, yet we lack clear guidance on where developers most need support and how to design it responsibly. We report a large-scale, mixed-methods study of N=860 developers examining where, why, and how they seek or limit AI across SE tasks. Using cognitive appraisal theory, we provide the first empirically validated mapping of developers’ task appraisals to AI adoption patterns and Responsible AI (RAI) priorities. Appraisals predict AI openness and use, revealing distinct patterns: strong current use and demand for improvement in core work (e.g., coding, testing); high demand to reduce toil (e.g., documentation, operations); and clear limits for identity- and relationship-centric work (e.g., mentoring). RAI priorities vary by context: reliability and security for systems-facing tasks; transparency, alignment, and steerability to maintain control; and fairness and inclusiveness for human-facing work. Our results offer concrete, contextual guidance for delivering AI where it matters to developers and their work.
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 428-439
Open AccessAI Where It Matters: Where, Why, and How Developers Want AI Support in Daily Work
Generative AI is reshaping software work, yet we lack clear guidance on where developers most need support and how to design it responsibly. We report a large-scale, mixed-methods study of N=860 developers examining where, why, and how they seek or limit AI across SE tasks. Using cognitive appraisal theory, we provide the first empirically validated mapping of developers’ task appraisals to AI adoption patterns and Responsible AI (RAI) priorities. Appraisals predict AI openness and use, revealing distinct patterns: strong current use and demand for improvement in core work (e.g., coding, testing); high demand to reduce toil (e.g., documentation, operations); and clear limits for identity- and relationship-centric work (e.g., mentoring). RAI priorities vary by context: reliability and security for systems-facing tasks; transparency, alignment, and steerability to maintain control; and fairness and inclusiveness for human-facing work. Our results offer concrete, contextual guidance for delivering AI where it matters to developers and their work.
- Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 171-175
Revealing the Dark Matter: Connecting Tacit and System Knowledge in Human-AI Collaborations
Software processes rely not only on well-documented artifacts like code, version histories, and logs, but also on team communications and tacit expertise that are rarely captured formally. We argue that effective human–AI collaboration requires shared knowledge spaces that integrate these sources and make their connections explicit. Using differential testing as a motivating case, we describe our initial prototype and the challenges it revealed, and outline a vision for dynamic knowledge spaces that support such collaboration.
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 171-175
Open AccessRevealing the Dark Matter: Connecting Tacit and System Knowledge in Human-AI Collaborations
Software processes rely not only on well-documented artifacts like code, version histories, and logs, but also on team communications and tacit expertise that are rarely captured formally. We argue that effective human–AI collaboration requires shared knowledge spaces that integrate these sources and make their connections explicit. Using differential testing as a motivating case, we describe our initial prototype and the challenges it revealed, and outline a vision for dynamic knowledge spaces that support such collaboration.
- Open Access
- 1 March 2026
- Published by Association for Computing Machinery (ACM) in Queue
- Vol. 24 (2)
Climbing the Generative AI Mountain
A “hitchhiker’s guide” for product managers
- 1 March 2026
- Published by Association for Computing Machinery (ACM) in Queue
- Vol. 24 (2)
Open AccessClimbing the Generative AI Mountain
A “hitchhiker’s guide” for product managers
- Open Access
Good Vibrations? A Qualitative Study of Co-Creation, Communication, Flow, and Trust in Vibe Coding
Vibe coding, a term coined by Andrej Karpathy in February 2025, has quickly become a compelling and controversial natural language programming paradigm in AI-assisted software development. Centered on iterative co-design with an AI assistant, vibe coding emphasizes flow and experimentation over strict upfront specification. While initial studies have begun to explore this paradigm, most focus on analyzing code artifacts or proposing theories with limited empirical backing. There remains a need for a grounded understanding of vibe coding as it is perceived and experienced by developers. We present the first systematic qualitative investigation of vibe coding perceptions and practice. Drawing on over 190,000 words from semi-structured interviews, Reddit threads, and LinkedIn posts, we characterize what vibe coding is, why and how developers use it, where it breaks down, and which emerging practices aim to support it. We propose a qualitatively grounded theory of vibe coding centered on conversational interaction with AI, co-creation, and developer flow and joy. We find that AI trust regulates movement along a continuum from delegation to co-creation and supports the developer experience by sustaining flow. We surface recurring pain points and risks in areas including specification, reliability, debugging, latency, code review burden, and collaboration. We also present best practices that have been discovered and shared to mitigate these challenges. We conclude with implications for the future of AI dev tools and directions for researchers investigating vibe coding.
Open AccessGood Vibrations? A Qualitative Study of Co-Creation, Communication, Flow, and Trust in Vibe Coding
Vibe coding, a term coined by Andrej Karpathy in February 2025, has quickly become a compelling and controversial natural language programming paradigm in AI-assisted software development. Centered on iterative co-design with an AI assistant, vibe coding emphasizes flow and experimentation over strict upfront specification. While initial studies have begun to explore this paradigm, most focus on analyzing code artifacts or proposing theories with limited empirical backing. There remains a need for a grounded understanding of vibe coding as it is perceived and experienced by developers. We present the first systematic qualitative investigation of vibe coding perceptions and practice. Drawing on over 190,000 words from semi-structured interviews, Reddit threads, and LinkedIn posts, we characterize what vibe coding is, why and how developers use it, where it breaks down, and which emerging practices aim to support it. We propose a qualitatively grounded theory of vibe coding centered on conversational interaction with AI, co-creation, and developer flow and joy. We find that AI trust regulates movement along a continuum from delegation to co-creation and supports the developer experience by sustaining flow. We surface recurring pain points and risks in areas including specification, reliability, debugging, latency, code review burden, and collaboration. We also present best practices that have been discovered and shared to mitigate these challenges. We conclude with implications for the future of AI dev tools and directions for researchers investigating vibe coding.
- Open Access
"Maybe We Need Some More Examples:" Individual and Team Drivers of Developer GenAI Tool Use
Despite the widespread availability of generative AI tools in software engineering, developer adoption remains uneven. This unevenness is problematic because it hampers productivity efforts, frustrates management's expectations, and creates uncertainty around the future roles of developers. Through paired interviews with 54 developers across 27 teams -- one frequent and one infrequent user per team -- we demonstrate that differences in usage result primarily from how developers perceive the tool (as a collaborator vs. feature), their engagement approach (experimental vs. conservative), and how they respond when encountering challenges (with adaptive persistence vs. quick abandonment). Our findings imply that widespread organizational expectations for rapid productivity gains without sufficient investment in learning support creates a "Productivity Pressure Paradox," undermining the very productivity benefits that motivate adoption.
Open Access"Maybe We Need Some More Examples:" Individual and Team Drivers of Developer GenAI Tool Use
Despite the widespread availability of generative AI tools in software engineering, developer adoption remains uneven. This unevenness is problematic because it hampers productivity efforts, frustrates management's expectations, and creates uncertainty around the future roles of developers. Through paired interviews with 54 developers across 27 teams -- one frequent and one infrequent user per team -- we demonstrate that differences in usage result primarily from how developers perceive the tool (as a collaborator vs. feature), their engagement approach (experimental vs. conservative), and how they respond when encountering challenges (with adaptive persistence vs. quick abandonment). Our findings imply that widespread organizational expectations for rapid productivity gains without sufficient investment in learning support creates a "Productivity Pressure Paradox," undermining the very productivity benefits that motivate adoption.
- Open Access
- 23 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 355-365
Using Large Language Models to Support the Workflow of Differential Testing
- 23 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 355-365
Open AccessUsing Large Language Models to Support the Workflow of Differential Testing
- Open Access
- 21 February 2025
- Published by Association for Computing Machinery (ACM) in Communications of the ACM
- Vol. 68 (3) , 34-41
Program Merge: What's Deep Learning Got to Do with It?
A discussion with Shuvendu Lahiri, Alexey Svyatkovskiy, Christian Bird, Erik Meijer and Terry Coatta
- 21 February 2025
- Published by Association for Computing Machinery (ACM) in Communications of the ACM
- Vol. 68 (3) , 34-41
Open AccessProgram Merge: What's Deep Learning Got to Do with It?
A discussion with Shuvendu Lahiri, Alexey Svyatkovskiy, Christian Bird, Erik Meijer and Terry Coatta