GitHub DevEx Research
Featured respondent in GitHub's landmark study on developer experience and productivity
The Research
In early 2024, GitHub published empirical DevEx research — a study conducted in partnership with DX that surveyed more than 20 industry-diverse companies to quantify how developer experience actually affects productivity and innovation.
The findings were striking: developers who protect deep work time felt 50% more productive. Those with high code comprehension felt 42% more productive. Fast feedback loops correlated with 50% less technical debt. This wasn’t opinion — it was data, published in ACM Queue and anchored by statistical analysis across real engineering organizations.
The paper
The full research, DevEx in Action: A Study of Its Tangible Impacts, was published in ACM Queue alongside this GitHub post.
My Involvement
I was connected to the research through Abi Noda and Greyson Junggren at DX, who introduced me to Eirini Kalliamvakou, the GitHub researcher leading the study. I was brought in as a featured respondent — someone actively leading DevEx work at scale — and quoted directly in the published piece.
At the time, I was deep in this exact problem space: how do you make the case, with data, that developer experience investments pay off? Having the chance to contribute my perspective to research that answered that question definitively felt meaningful.
Why It Matters
One of the hardest parts of DevEx work is the justification problem. You’re asking organizations to invest in things that feel intangible — flow state, cognitive load, feedback loops — and the ROI isn’t always obvious to stakeholders who haven’t felt the friction themselves.
This research gives practitioners like me a vocabulary and a evidence base to have those conversations. When I say that reducing cognitive load makes developers more productive, I can now point to the data. That changes the conversation entirely.