--- title: Measuring developer productivity with the DX Core 4 description: The DX Core 4 is a unified developer productivity measurement framework that combines DORA, SPACE, and DevEx into four dimensions: speed, effectiveness,... canonical: https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Measuring developer productivity with the DX Core 4 | daily.dev og:description: The DX Core 4 is a unified developer productivity measurement framework that combines DORA, SPACE, and DevEx into four dimensions: speed, effectiveness,... og:url: https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey og:image: https://api.daily.dev/og/posts/ZDWsim4eY.png og:image:alt: Measuring developer productivity with the DX Core 4 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Measuring developer productivity with the DX Core 4 **[Hacker News](https://daily.dev/sources/hn)** · 7 min read · 0 upvotes · 0 comments ## Summary The DX Core 4 is a unified developer productivity measurement framework that combines DORA, SPACE, and DevEx into four dimensions: speed, effectiveness, quality, and business impact. Designed to be deployable in weeks rather than months, it uses a mix of system metrics, self-reported data, and experience sampling. Key features include multi-dimensional counterbalancing to prevent gaming, applicability at all organizational levels, and a cautious approach to throughput metrics like diffs per engineer. The framework has been adopted at over 300 organizations, reportedly yielding 3–12% gains in engineering efficiency and 14% more R&D time on feature development. Practical guidance covers establishing baselines quickly with self-reported data, starting small, and communicating transparently with teams. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community take How the wider developer community reacted, aggregated from 1 discussion and 51 comments across hackernews (as of 2026-07-27). **TL;DR:** The HN community is largely skeptical of developer productivity metrics like DX Core 4, warning about Goodhart's Law, worker surveillance, and perverse incentives — though a minority see value in well-intentioned, survey-based approaches used to improve developer experience rather than punish individuals. **Sentiment:** 15% positive · 30% mixed · 55% skeptical **The case for** - Metrics can help justify tooling investments and identify genuine friction points when used transparently and for improvement rather than punishment. - Survey-based subjective measures (e.g., 'do you feel productive?') can be as reliable as hard metrics and less gameable. - Some teams report useful signals from DX about internal dev tooling and onboarding effectiveness. **The pushback** - Developers will game any metric tied to their livelihood (e.g., smaller PRs, more commits), rendering the data meaningless — Goodhart's Law. - Metrics like diffs/PRs per engineer ignore valuable non-coding contributions such as mentoring, design, and code review quality. - Surveillance-style measurement and constant self-justification create anxiety, reduce morale, and drive away the most productive employees first. - Non-technical managers using these tools as a substitute for understanding actual output signals a deeper management competence problem. - In-context sampling and flow-state interruptions create bad incentives and unhealthy work cycles. **By community** - hackernews (skeptical): Commenters are predominantly critical, citing Goodhart's Law, worker alienation, and perverse incentives, with only a few voices defending transparent, survey-driven use of the tool. **Hottest debate:** Whether any developer productivity metric can avoid being gamed or weaponized against workers versus being genuinely useful for improving developer experience. **Open questions** - Why does GetDX avoid prominently disclosing its Atlassian ownership in promotional material? - What metrics, if any, could capture non-coding contributions like mentoring and design without creating perverse incentives? - Should management productivity be measured alongside developer productivity? **Highlights** > And if you start measuring amount of commits or PR's I'd bet money on there suddenly being smaller PR's and more commits. As soon as the metric is tied to peoples livelihood, it will be gamed. Funny anecdote: I had a large company selling their LLM tools with a slideshow starting with a mention of Goodhart's Law, and then proudly present number of PR's as a metric in the next slide. > — [tripledry on hackernews](https://news.ycombinator.com/item?id=49068300) > Basically every company I’ve worked for has had some sort of rubric like this. I don’t think that’s inherently bad, it can be quite good for consistency. I have quit companies that made their performance review systems too onerous/frequent/intense. It’s exhausting to constantly be justifying your existence and having to sell yourself instead of doing the real work. At one point I was at a 50/50 ratio of time spent documenting/justifying my work vs doing my work, and that was miserable. My level of anxiety reduced my job performance, which created a very unhealthy cycle. Pressure creates diamonds but it also suffocates and crushes most things. That’s why seeing things like in-context sampling in the article make me suspicious. I don’t think I would be happy at all being interrupted as I’m in flow state to be asked if I could be more productive. I also feel some of this like speed (“time to 10th PR”) or working on new stuff is creating bad incentives. Fundamentally the most important metric is how hard your boss will fight for you. The second most important metric is whether you can meaningfully discuss areas of improvement honestly and safely with your boss. If either of those two are out of whack you should question whether to make a change. If I’m missing those I’m not going to be able to do my best work, so it cuts both ways. > — [data-ottawa on hackernews](https://news.ycombinator.com/item?id=49068856) > my current place uses DX and it's well received, if done transparently and for the right reasons. there's a lot of very interesting research in these areas (e.g. EngThrive) where the focus is on measuring things that if gamed result in better outcomes there's strong correlation when onboarding an engineer between the time to first/tenth/fiftieith PR and their PR throughput two years later, so the answer is make it really easy to do PRs when onboarding, and they saw the same outcome even if those initial PRs were trivial through DORA/SPACE/DevEx they also found that asking your engineers if they feel productive is generally as useful and reliable than trying to measure every possible dimension - which is why DX is based largely around the survey with subjective responses. if you actually use those responses to address friction and frustration, from my experience you end up with more, better, easier work getting done it's possible to work in a team that cares about measuring their effectiveness, and using those measurements to understand how to be more effective. most/all engineers will have an idea of how they could improve their work, but the reality when you actually spend time to measure often shows a lot of different things you might not have been aware of > — [aevv on hackernews](https://news.ycombinator.com/item?id=49069984) > I would like to present DX team another metric. It is called "not wanting to work in a company that is insulting me with measures like metrics, spying on screens, squeezing every drop of sweat and exploiting its workers for already huge profit. My last job change was exactly due to company acquisition by USA company that started to exploit everything work related, removing wfh, ruining life-job ballance,... And who leaves first? Those who can. So you are not really measuring developer productivity but helping company get rid of most productive people, while all others stay. > — [stiray on hackernews · 4 comments](https://news.ycombinator.com/item?id=49067421) > That's exactly what they're introducing all of that crap for, to make people quit voluntarily, layoffs are more expensive... > — [Anonyneko on hackernews](https://news.ycombinator.com/item?id=49068563) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49033522) · 26 points · 51 comments ## Similar posts on daily.dev - [Revisiting the DX Core 4 in the age of AI](https://daily.dev/posts/revisiting-the-dx-core-4-in-the-age-of-ai-somz6v8fn) · Engineering Enablement · 6 upvotes · 0 comments - [AI’s biggest impact isn’t cranking out more code: Why DevEx matters](https://daily.dev/posts/ai-s-biggest-impact-isn-t-cranking-out-more-code-why-devex-matters-thxks9swh) · Dynatrace · 0 upvotes · 0 comments - [5 pitfalls to avoid when measuring developer experience in the AI era](https://daily.dev/posts/5-pitfalls-to-avoid-when-measuring-developer-experience-in-the-ai-era-jpu9ct3gf) · Datadog · 0 upvotes · 0 comments - [How To Measure the ROI of Developer Tools](https://daily.dev/posts/how-to-measure-the-roi-of-developer-tools-xnkov1ooc) · CNCF · 6 upvotes · 0 comments --- Tags: [#devtools](https://daily.dev/tags/devtools), [#dora](https://daily.dev/tags/dora), [#dora-metrics](https://daily.dev/tags/dora-metrics), [#leadership](https://daily.dev/tags/leadership), [#productivity](https://daily.dev/tags/productivity) [View this post on daily.dev](https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Measuring developer productivity with the DX Core 4","url":"https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey"},"datePublished":"2026-07-27T10:27:54.167Z","dateModified":"2026-10-14T02:35:45.492Z","description":"The DX Core 4 is a unified developer productivity measurement framework that combines DORA, SPACE, and DevEx into four dimensions: speed, effectiveness,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4a31f64c04dfc68fe62f9ba8f2bdd320?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4a31f64c04dfc68fe62f9ba8f2bdd320?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/measuring-developer-productivity-with-the-dx-core-4-zdwsim4ey","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"devtools,dora,dora-metrics,leadership,productivity","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Measuring developer productivity with the DX Core 4"}]} ```