The hottest Productivity Metrics Substack posts right now

And their main takeaways
Category
Top Business Topics

Are AI Coding Assistants Really Saving Developers Time? Study Suggests These Tools Don’t Increase Coding Speed.

Shenisha’s Substack • 19 implied HN points • 04 Oct 24
🕹 Technology Productivity Metrics
  1. AI coding tools, like GitHub Copilot, may actually slow down developers by increasing the number of bugs in their code. This raises questions about whether these tools truly help improve code quality.
  2. While some surveys show that many developers use AI tools and feel productive, a study found that these tools didn't significantly improve coding speed or help reduce burnout among developers.
  3. The rise of AI tools may require developers to spend more time reviewing the code these tools produce, which can cancel out any time they might save overall.

AI productivity gains are 10%, not 10x

Engineering Enablement • 23 implied HN points • 11 Mar 26
🕹 Technology Productivity Metrics
  1. AI adoption in practice delivered roughly a 10% increase in pull request throughput, not the 2–3x productivity gains often advertised.
  2. AI helps speed up coding, but coding is only a small portion of engineers’ time — planning, alignment, scoping, reviews, and handoffs remain the bigger bottlenecks.
  3. Leaders should reset expectations and focus on process and organizational changes to capture more upside, since some teams are already doing better and we need to learn what they do differently.

AI tooling benchmarks: PR throughput and usage by tool (Q1 2026)

Engineering Enablement • 11 implied HN points • 21 Jan 26
🕹 Technology Productivity Metrics
  1. AI-native, agentic coding tools are driving the biggest increases in PR throughput. Cursor, Claude, and GitHub Copilot showed notable quarter-over-quarter gains while Tabnine registers lower throughput, often in large enterprises.
  2. Adoption patterns vary by cadence: Copilot is the stickiest daily driver, Cursor is becoming a primary weekly workspace, and tools like Windsurf and Tabnine are used more monthly for specialized tasks.
  3. Organizations should correlate tool usage with PR throughput and measure ROI rather than counting seats alone. A multi-vendor approach and stronger practices are recommended because technical limits and policy gaps still constrain productivity gains.

DevProd headcount benchmarks, Q1 2026

Engineering Enablement • 10 implied HN points • 07 Jan 26
🕹 Technology Productivity Metrics
  1. Most companies dedicate about 2–6% of engineering headcount to centralized developer productivity, averaging roughly 4.7%, and that percentage tends to shrink as organizations grow past ~1,000 engineers because tooling, automation, and leverage reduce headcount needs.
  2. The benchmark counts only narrowly-defined DevProd teams (internal developer platforms, DevEx/Productivity, build & release, test infra, and developer education/support) and excludes SRE, general cloud, security, and product-facing platform teams.
  3. Treat these numbers as a guideline, not a quota: use them to set initial headcount for a center of excellence and pair them with measurement (for example, the Core 4) to confirm the team is actually reducing developer friction.

AI and productivity: Year-in-review with Microsoft, Google, and GitHub researchers

Engineering Enablement • 13 implied HN points • 17 Dec 25
🕹 Technology Productivity Metrics
  1. Lines of code is a poor measure of AI’s value — more output doesn’t equal more impact. Use broader measures like satisfaction, performance, collaboration, and efficiency to judge whether AI actually helps.
  2. AI is changing the developer role from code producer to director and validator of AI-assisted work, so hiring, career paths, and training must prioritize AI fluency, systems thinking, and judgment. Juniors might learn end-to-end problem solving faster, but only if teams preserve mentorship and opportunities to collaborate.
  3. The real wins come from enablement and focusing AI on real bottlenecks or tedious work, not from constantly switching tools or models. Also, don’t trust simple headlines — dig into context, and design tools to boost creativity and meaningful automation rather than just raw speed.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Measuring the Productivity of Developers

burkhardstubert • 39 implied HN points • 04 Oct 23
🕹 Technology Productivity Metrics
  1. McKinsey suggests measuring developer productivity using new metrics that track time spent on development versus other tasks. This way, they want to see more time in real coding and less in meetings.
  2. Orosz and Beck argue that measuring effort or output isn't very useful because people might manipulate those numbers. Instead, they say to focus on the actual effects of the work, like the value that reaches customers.
  3. Team performance is more important than individual effort. It's better to measure how well a team works together than to judge each person separately.

Measuring developer productivity: A clear-eyed view

Engineering Enablement • 21 implied HN points • 05 Feb 25
🕹 Technology Productivity Metrics
  1. Metrics for developers should help improve their work experience, not just measure their output. Goodhart's Law reminds us that once metrics are tied to rewards, they can become misleading.
  2. Developer experience is more about effectiveness than happiness. Measuring how developers feel needs to focus on the frustrations they face, and not just on making them comfortable.
  3. Using benchmarks is important but context is key. Just like medical tests, numbers need interpretation to make sense; comparing different teams requires understanding their unique challenges.

The DX Core 4 Framework

Fish Food for Thought • 11 implied HN points • 11 Dec 24
🕹 Technology Productivity Metrics
  1. The DX Core 4 Framework helps companies measure developer productivity by looking at four main areas: Speed, Effectiveness, Quality, and Impact. This balanced approach provides a complete picture of how well teams are performing.
  2. It includes a Developer Experience Index (DXI) that shows how developers feel about their work, helping identify areas for improvement. This means companies can catch issues before they become bigger problems.
  3. The framework focuses on connecting developer productivity to business goals, making it easier for all levels of the organization to understand how engineering work impacts the company's success.