Ciera Jaspan

Ciera Jaspan

Auto-generated profile, based on publicly available information

Ciera Jaspan

Engineering Productivity Research team, Google, Mountain View, CA, USA

Research Focus & Metrics

Academic Career Length

18Years (2009-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
19 February 2019 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
EMEmerson Murphy-Hill
Emerson Murphy-Hill
CJCiera Jaspan
Ciera Jaspan
CSCaitlin Sadowski
Caitlin Sadowski
DSDavid Shepherd
David Shepherd
MPMichael Phillips
Michael Phillips
MJMatthew Jorde
Matthew Jorde

10 July 2024
Verified
Conference Paper
Open access
ABAdam Brown
Adam Brown
SDSarah D'ANgelo
Sarah D'ANgelo
AMAmbar Murillo
Ambar Murillo
CJCiera Jaspan
Ciera Jaspan
CGCollin Green
Collin Green
AI-powered software development tooling is changing the way that developers interact with tools and write code. However, the ability for AI to truly transform software development may depend on developers' levels of trust in these tools, which has consequences for tool adoption and repeated usage. In this work, we take a mixed-methods approach to measure the factors that influence developers' trust in AI-powered code completion. We found that characteristics about the AI suggestion itself (e.g., the quality of the suggestion), the developer interacting with the suggestion (e.g., their expertise in a language), and the context of the development work (e.g., was the suggestion in a test file) all influenced acceptance rates of AI-powered code suggestions. Based on these findings we propose a number of recommendations for the design of AI-powered development tools to improve trust.

26 April 2023 in IEEE Software
Verified
Journal Article
Closed access
CJCiera Jaspan
Ciera Jaspan
CGCollin Green
Collin Green
Ward Cunningham introduced the metaphor underlying the term technical debt in a 1992 experience report, where he described how his company incrementally extended a piece of financial software:

5 August 2020 in IEEE Software
Verified
Journal Article
Open access
CJCiera Jaspan
Ciera Jaspan
MJMatt Jorde
Matt Jorde
CECarolyn D Egelman
Carolyn D Egelman
CGCollin Green
Collin Green
BHBen Holtz
Ben Holtz
EKElizabeth Kammer
Elizabeth Kammer
Understanding developers’ day-to-day behavior can help answer important research questions, but capturing that behavior at scale can be challenging, particularly when developers use many tools in concert to accomplish their tasks. In this paper, we describe our experience creating a system that integrates log data from dozens of development tools at Google, including tools that developers use to email, schedule meetings, ask and answer technical questions, find code, build and test, and review code. The contribution of this article is a technical description of the system, a validation of it, and a demonstration of its usefulness.

4 June 2024 in IEEE Software
Verified
Journal Article
Closed access
SDSarah D’aNgelo
Sarah D’aNgelo
JLJessica Lin
Jessica Lin
JDJill Dicker
Jill Dicker
CECarolyn Egelman
Carolyn Egelman
MHMaggie Hodges
Maggie Hodges
CJCiera Jaspan
Ciera Jaspan
At Google, we’ve been running a quarterly large-scale survey with developers since 2018. In this article, we will discuss how we run EngSat, some of our key learnings over the past 6 years, and how we’ve evolved our approach to meet new needs and challenges.

19 April 2023
Verified
Conference Paper
Open access
ABAdam Brown
Adam Brown
SDSarah D'ANgelo
Sarah D'ANgelo
BHBen Holtz
Ben Holtz
CJCiera Jaspan
Ciera Jaspan
CGCollin Green
Collin Green
Beyond self-report data, we lack reliable and non-intrusive methods for identifying flow. However, taking a step back and acknowledging that flow occurs during periods of focus gives us the opportunity to make progress towards measuring flow by isolating focused work. Here, we take a mixed-methods approach to design a logs-based metric that leverages machine learning and a comprehensive collection of logs data to identify periods of related actions (indicating focus), and validate this metric against self-reported time in focus or flow using diary data and quarterly survey data. Our results indicate that we can determine when software engineers at a large technology company experience focused work which includes instances of flow. This metric speaks to engineering work, but can be leveraged in other domains to non-disruptively measure when people experience focus. Future research can build upon this work to identify signals associated with other facets of flow.