Developer Experience != Developer Productivity Metrics

Developer Experience is more than just Productivity metrics FOSDEM 2026 - Testing & CD DevRoom

DevEx disasters… FOSDEM 2026 - Testing & CD DevRoom

git push heroku main FOSDEM 2026 - Testing & CD DevRoom

Jeremy Meiss Director, DevEx & DevRel OneStream Software DevOpsDays KC Organizer FOSDEM 2026 - Testing & CD DevRoom

FOSDEM 2026 - Testing & CD DevRoom

ity v ti c u d ro P r e p lo e v e D e vs Developer Experienc Developer Experience Developer Productivity _”…the journey of developers as they learn and deploy technology, which if successful, focuses on eliminating obstacles that hinder a developer or practitioner from achieving success in their endeavors.” “Developer productivity refers to the effectiveness and efficiency with which software developers produce high-quality code and complete projects.”” -Jessica West, Director of Education & Customer Experience (Chronosphere) FOSDEM 2026 - Testing & CD DevRoom LinearB

vity ti c u d ro P r e p lo e v e D e != Developer Experienc 🎵 More than a metric…. 🎵 Experience is the Cause 🌳 The Roots: DevEx The daily journey: tools, processes, cognitive load, and flow state. FOSDEM 2026 - Testing & CD DevRoom Productivity is the Effect 🍎 The Fruit: Productivity The outcome: high-quality, impactful software that drives business value.

DevEx isn’t new REF: F. Fagerholm and J. Münch, “Developer experience: Concept and definition,” 2012 International Conference on Software and System Process (ICSSP), Zurich, Switzerland, 2012. FOSDEM 2026 - Testing & CD DevRoom

DevEx isn’t new “New ways of working such as globally distributed development or the integration of self-motivated external developers into software ecosystems will require a better and more comprehensive understanding of developers’ feelings, perceptions, motivations and identification with their tasks in their respective project environments.” REF: F. Fagerholm and J. Münch, “Developer experience: Concept and definition. 2012.” FOSDEM 2026 - Testing & CD DevRoom

DevEx isn’t new “…developer experience could be defined as a means for capturing how developers think and feel about their activities within their working environments, with the assumption that an improvement of the developer experience has positive impacts on characteristics such as sustained team and project performance.” REF: F. Fagerholm and J. Münch, “Developer experience: Concept and definition. 2012.” FOSDEM 2026 - Testing & CD DevRoom

From Lines of Code to Value Streams !!! 1st 3 Leaders agree that traditional metrics like LOC are ineffective. Principle of modern measurement: Focus on systems, not just individuals. Prominent frameworks now guide the industry: DORA, SPACE, and GetDX Core 4. FOSDEM 2026 - Testing & CD DevRoom

Evolution of “Developer Experience” Frameworks FOSDEM 2026 - Testing & CD DevRoom

Comparing the Developer Productivity Frameworks DORA SPACE GetDX Core 4 Scope: Scope: Scope: Narrow. The software delivery pipeline (commit to deploy). Broad. The entire socio-technical system. Philosophy: Philosophy: Hybrid. Bridges engineering activity to business impact. Flexible. A menu of dimensions to choose from. Prescriptive. A unified recipe of 4 pillars. Audience: Audience: Engineering Management. Fosters empathetic conversations. The Entire Org. A shared language for engineers and C-suite. Data: Data: Hybrid. System data plus qualitative surveys. Hybrid. System data, surveys, and financial data. Prescriptive. A clear recipe of 4 key metrics. Audience: Technical Leaders. DevOps, SREs, Engineering Managers. Data: Quantitative. System data from CI/CD, Git, etc. FOSDEM 2026 - Testing & CD DevRoom Philosophy:

The Three Pillars of World-Class DevEx Fast, HighQuality Feedback Loops Slow, ambiguous feedback is a primary source of frustration. The speed of the inner loop (local build/test) and outer loop (CI/CD, code review) is critical for maintaining momentum and iterating with confidence. FOSDEM 2026 - Testing & CD DevRoom Low Cognitive Load Enabled “Flow State” Human working memory is limited. When developers must wrestle with complex systems or poor documentation, less mental energy is available for creating solutions. High rework is a strong signal of high cognitive load. Flow, or being “in the zone,” is where deep, creative work happens. It requires clear goals, immediate feedback, and protection from interruptions. It can take over 15 minutes to regain focus after a single interruption.

Fast, High-Quality Feedback Loops 1. Automated Visual Regression Testing in CI/CD 2. “Shifting Left” with Static Code Analysis and Linting in the IDE & Pre-Commit Hooks 3. Production “Canary” Deployments & Automated Monitoring with Meaningful Metrics 4. Daily “Mob Programming” or Pair Programming Sessions for Critical/Complex Tasks 5. Dedicated “Bug Bash” Weeks or Sprints with Stakeholder Involvement FOSDEM 2026 - Testing & CD DevRoom

Low Cognitive Load 1. Standardize Code Style & Linting Rules 2. Implement Version Control with Meaningful Commit Messages 3. Prioritize and Refactor Technical Debt Incrementally 4. Centralize Documentation and Knowledge Sharing 5. Implement Automated Testing at All Levels FOSDEM 2026 - Testing & CD DevRoom

Enabled “Flow State” 1. Implement a High-Signal Notification System & Prioritization 2. Adopt a Streamlined Code Review Process with Contextual Tooling 3. Standardize Development Environments and Automate Setup 4. Implement Short, Focused “Pomodoro” or Timeboxing Sessions 5. Cultivate a Culture of Psychological Safety and Open Communication FOSDEM 2026 - Testing & CD DevRoom

So what do we measure? Avoid the Gamification Trap Use Metrics for Improvement, Not Judgment “when a measure becomes a target, it ceases to be a good measure.” -Goodhart’s Law FOSDEM 2026 - Testing & CD DevRoom

So what do we measure? Cycle Time PR Review Time Rework Rate Meeting Load Time to First Commit Perceived Focus Time These are not one-size-fits-all metrics, but a starting point. FOSDEM 2026 - Testing & CD DevRoom

Cycle Time ⏱️ Implement and enforce “Small Batch” Size Approach Invest in Test Automation and CI/CD Pipelines Improve Dev Environment Setup and Standardization Proactively Identify and Remove Blocking Issues FOSDEM 2026 - Testing & CD DevRoom

PR Review Time 🔄 Enforce “Small PR” Guidelines and Automation Implement a Reviewer Rotation and/or “Reviewer Roulette” System Mandate Clear and Concise PR Descriptions and Context Establish and Make Visible SLAs for PR Reviews FOSDEM 2026 - Testing & CD DevRoom

Rework Rate ✍️ Refine User Stories with Clearer Acceptance Criteria and Examples Invest in Better Tooling and Automation for Testing Implement a Robust Definition of Done (DoD) and Enforce It Improve Feedback Loops and Communication FOSDEM 2026 - Testing & CD DevRoom

Meeting Load 🧠 Implement a “Meeting-Free Day” (or Half-Day) Policy Audit Meeting Invitations and Participation Standardize Meeting Agendas and Timeboxing Promote Asynchronous Communication Tools & Practices Implement a “Meeting Budget” or “Meeting Credit” System FOSDEM 2026 - Testing & CD DevRoom

Time to First Commit 🚀 Provide Ready-to-Run Starter Projects/Templates Automate Environment Setup and Onboarding Simplify Code Contribution with Clear Guidelines and Tooling Offer Short, Focused “First Contribution” Tasks Provide Active Mentorship and Support (paired with tooling) FOSDEM 2026 - Testing & CD DevRoom

Perceived Focus Time 💡 Optimize Build Times with Incremental Builds and Caching Prioritize and Reduce Notification Overload Automate Repetitive Tasks with Scripting or Tools Improve Error Messaging and Debugging Tools FOSDEM 2026 - Testing & CD DevRoom

Cycle Time PR Review Time Rework Rate Meeting Load Time to First Commit Perceived Focus Time FOSDEM 2026 - Testing & CD DevRoom

Build a Healthy Measurement Culture No framework is a silver bullet Continuous improvement, not judgment Communicate the ‘why’ Involve your team Focus on trends, not absolutes Combine quantitative data with qualitative human insights FOSDEM 2026 - Testing & CD DevRoom

Conclusion FOSDEM 2026 - Testing & CD DevRoom

DevEx is… “ruthlessly eliminating barriers (and blockers) that keep your practitioners from being successful” FOSDEM 2026 - Testing & CD DevRoom

@jerdog.dev /in/jeremymeiss Thank you! @jerdog @jerdog@hachyderm.io jmeiss.me FOSDEM 2026 - Testing & CD DevRoom

END FOSDEM 2026 - Testing & CD DevRoom