coding is a communal activity
coding is a communal activity
coding is a communal activity
with
Practical Application Facilitation Guides
I collaborate closely with the Developer Success Lab research team to produce original empirical research on how software teams and developers learn, work and thrive. This team's research agenda tackles far-reaching, meaningful questions in the intersection of behavioral science and software research.
​
As the Principal Developer Experience Engineer on this team, I work directly with our research scientists to design original materials, workshops, interventions and curricula that drive productive behavior change on software teams. Here, you can access facilitation guides that I've created both independently and in collaboration with the Developer Success Lab.
01
This Generative-AI Adoption Toolkit is meant to answer an important question for today’s technology leaders: How can I help my team adopt AI-assisted coding tools and practices in a human-centered and evidence-based way?
​
This toolkit enables engineering leaders to seize on this tidal wave of change in a way that keeps developers front of mind, by tackling AI Skill Threat head-on. It contains evidence-based, human-centered resources to help you put the research-backed Developer Thriving Framework into practice.
The components of this toolkit represent adaptations of well-known software ceremonies: post-mortems and hackathons. Learning, belonging, collaboration, and community are already built into these long-practiced ceremonies. Our research has found that two key elements in the Developer Thriving framework – learning cultures and sense of belonging – strengthen developers’ resilience as they transition to AI-assisted software development. In this toolkit, we’ll guide you through increasing learning and belonging on your teams, and give you detailed plans, rationales and scripts to confidently lead these experiences.
02
Software development teams traditionally use the retrospective ceremony to reflect on their results, performance and processes. But the software team retrospective can – and should – periodically focus on team-level concerns beyond these traditional themes.
In the summer of 2022, I led a learning-themed retrospective with my engineering team that encouraged my teammates to reflect on their personal beliefs about on-the-job learning, our team’s learning culture, and the ways in which these beliefs and culture can both encourage and discourage engagement in on-the-job learning and upskilling activities.
Through this exercise, my team began to identify the strengths and weaknesses in our learning culture, as well as if, how and why we were accumulating personal and team-wide learning debt.
