Maggie Hodges

Maggie Hodges

Auto-generated profile, based on publicly available information

Maggie Hodges

Google, Mountain View, CA, USA

Research Focus & Metrics

Academic Career Length

4Years (2023-Present)

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

Representative Publications

View All Publications
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.

14 April 2023 in Proceedings of the ACM on Human-Computer Interaction
Verified
Journal Article
Open access
EMEmerson Murphy-Hill
Emerson Murphy-Hill
JDJillian Dicker
Jillian Dicker
AHAmber Horvath
Amber Horvath
MHMaggie Morrow Hodges
Maggie Morrow Hodges
CECarolyn D. Egelman
Carolyn D. Egelman
NCNina Chen
Nina Chen
Code review is an essential task for modern software engineers, where the author of a code change assigns other engineers the task of providing feedback on the author's code. In this paper, we investigate the task of code review through the lens of equity, the proposition that engineers should share reviewing responsibilities fairly. Through this lens, we quantitatively examine gender inequities in code review load at Google. We found that, on average, women perform about 25% fewer reviews than men, an inequity with multiple systemic antecedents, including authors' tendency to choose men as reviewers, a recommender system's amplification of human biases, and gender differences in how reviewer credentials are assigned and earned. Although substantial work remains to close the review load gap, we show how one small change has begun to do so.

6 October 2023 in IEEE Software
Verified
Journal Article
Open access
CGCollin Green
Collin Green
CJCiera Jaspan
Ciera Jaspan
MHMaggie Hodges
Maggie Hodges
LHLanting He
Lanting He
DSDemei Shen
Demei Shen
NZNan Zhang
Nan Zhang
In our column thus far, we’ve focused on understanding and measuring productivity in a human-centered manner.1 Along the way, we have noted that the productivity of less senior and less tenured developers is, at least in some cases, sensitive to different pressures (or differentially sensitive to the same pressures) as that of their more senior and more tenured colleagues.2 This finding is intuitive: developers that are earlier in their career are typically assigned different tasks, they have less variety of experience to draw upon when faced with technical or organizational obstacles, and they may be less familiar with relevant tools, infrastructure, languages, libraries, and processes when compared to their more experienced fellow engineers. But how does a developer go from a rookie to a veteran? What facilitates or hinders developer onboarding and ramp-up? How can one assess interventions aimed at speeding up or otherwise improving developer training and education so that new engineers are enabled to hit their productivity stride quicker and more easily?