DX Blog
getdx.com · Company blog · on HN since 2022
Company blog of DX, a developer productivity analytics firm now part of Atlassian, covering engineering metrics, developer experience and platform teams.
What HN saysHN commenters debate its Core 4 and SPACE metrics, with some objecting to measuring individual developers, and others discussing AI's effect on productivity.
19HN people shared it
8linked it in comments
17stories submitted
47story points
3 months agolast shared
2022people per year2026
Most-shared posts
- 1Motivating Developers to Care About Documentation2 people · 17 points · first shared 2022 · 4 comments on HN
- 2DX Is Joining Atlassian2 people · 6 points · first shared 2025 · discussion on HN
- 3Measuring developer productivity with the DX Core 42 people · 2 points · first shared 2026 · discussion on HN
- 4The Engineering Enablement Podcast2 people · 1 points · first shared 2022 · discussion on HN
- 5Homepage2 people · first shared 2023
- 6A new framework for measuring developer productivity1 people · 4 points · first shared 2024 · discussion on HN
- 7Platform team challenges, realigning on DevEx, and change management1 people · 3 points · first shared 2024 · discussion on HN
- 8How to Get Buy-In for DevEx Initiatives: Strategies from GitHub,Notion,and More1 people · 2 points · first shared 2023 · discussion on HN
- 9Space Framework, PRs per Engineer, AI Research – Brian Houck (Microsoft)1 people · 2 points · first shared 2024 · discussion on HN
- 10CTO buy-in, measuring sentiment, and customer focus1 people · 2 points · first shared 2024 · discussion on HN
- 11DX: the world’s first developer experience platform1 people · 2 points · first shared 2022 · 1 comments on HN
- 12An Actionable Framework for Understanding and Improving Developer Experience [pdf]1 people · 2 points · first shared 2022 · discussion on HN
- 13An inside look at the SPACE framework1 people · 1 points · first shared 2023 · discussion on HN
- 14A Better Way to Measure Developer Productivity1 people · 1 points · first shared 2023 · discussion on HN
- 15Why lines of code are a bad measure of developer productivity1 people · 1 points · first shared 2024 · 1 comments on HN
What HN people wrote when they linked it
manfre · 2026-06-15
It's a combination of different activity metrics (commits, PRs, comments, etc) with AI thrown in to figure out substance/complexity of the work. I originally thought the summaries were simple metrics without factoring quality. There are products that provide this for github and other tools. E.g. https://getdx.com/
2rsf · 2023-10-03
But also not directly to developer's experience.
Try the SPACE framework [1] from the same people, Nicole Forsgren et al.
It is more of a survey than measurable objective metrics, and the problem is with the implementation, like any other survey- build good questions, operating the survey analysis and results etc.
There some comercial tools available, for example getdx [2]
[1] https://queue.acm.org/detail.cfm?id=3454124
[2] https://getdx.com/
classictraffic · 2026-08-15
To the author’s point about there not being enough evidence to support pro-AI claims — Additionally, there are studies and articles coming out showing those people are wrong and AI only makes people barely more efficient. Not the 10x tech CEOs are claiming while slashing thousands of jobs
https://getdx.com/blog/ai-productivity-gains-are-10-percent-not-10x/
CraigJPerry · 2026-07-10
> Core 4 (and similar) rub me the wrong way – measuring individual developers as the atomic unit IMO is always meaningless
And From: https://getdx.com/research/measuring-developer-productivity-with-the-d…
> Diffs per engineer*
>
> * Not at individual level
Are you guys agreeing or disagreeing with each other?
keeda · 2026-02-19
Let's also not forget the multiple other studies that found significant boosts to productivity using rigorous methods like RCTs.
However, because these threads always go the same way whenever I post this, I'll link to a previous thread in hopes of preempting the same comments and advancing the discussion! https://news.ycombinator.com/item?id=46559254
Also, DX (whose CTO was giving the presentation) actually collects telemetry-based metrics (PR's etc.) as well: https://getdx.com/uploads/ai-measurement-framework.pdf
It's not clear from TFA if these savings are self-reported or from DX metrics.
KallDrexx · 2025-12-09
The latest survey is here apparently: https://getdx.com/report/ai-assisted-engineering-q4-impact-report/.
No idea if signing up gives the full survey for free. We get it through our company paying for DX's services
geekjock · 2024-01-25
"Lines of code is a much better proxy than reported productivity."
Researchers who specialize in this field largely disagree with this. Here's a round-up: https://getdx.com/blog/measuring-developer-activity/
esafak · 2023-12-28
You can't do all this alone; you need allies. So use your communication skills to persuade a suitable sponsor with the power to assign the necessary resources. Google and DX regularly release reports about these things; e.g., https://getdx.com/blog/documentation-culture-engineering/
You could use them to raise awareness in your organization.