More Dev Interrupted episodes

Stop measuring AI adoption. Start measuring AI impact. | LinearBs APEX framework thumbnail

Stop measuring AI adoption. Start measuring AI impact. | LinearBs APEX framework

Published 7 Apr 2026

Duration: 00:42:26

The APEX framework addresses AI integration in engineering by prioritizing AI Leverage, Predictability, Efficiency, and Developer Experience to balance productivity gains with workflow alignment, code quality, and team satisfaction through targeted metrics.

Episode Description

Are your AI coding tools actually making your team faster, or are they just creating downstream chaos? This week, Ben Lloyd Pearson and Dan Lines intr...

Overview

The text discusses the APEX framework, developed to address the challenges of integrating AI into modern software development. It highlights the growing influence of AI coding tools like Copilot and Claude, which are reshaping engineering workflows but also creating uncertainties about their real-world productivity gains. Traditional metrics like DORA, while foundational, are seen as insufficient for measuring AIs unique impacts on delivery speed, code quality, and business value. The APEX framework aims to bridge this gap by providing a practical, real-world-oriented model that incorporates AI as a core component of the software development lifecycle (SDLC). It focuses on four pillars: AI Leverage (how effectively AI is embedded in production systems), Predictability (ensuring reliable sprint commitments), Efficiency (optimizing code delivery and resource use), and Developer Experience (DevX) (balancing AI integration with developer satisfaction and workflow friction). By combining AI metrics with traditional SDLC pillars, APEX emphasizes a holistic approach to evaluating AIs role in engineering, ensuring it aligns with organizational goals without overhyping capabilities.

The discussion also underscores challenges in AI adoption, such as the illusion of speed created by AI tools, where upstream productivity gains are offset by downstream bottlenecks like unreviewed pull requests or unprepared deployment systems. The framework stresses the need for foundational stability firstprioritizing predictability and efficiency before layering AI toolsto avoid disruptions in workflow. It highlights the importance of metrics like AI-assisted pull request rates, cycle time, and defect rates to measure AIs actual impact, rather than focusing solely on usage. Additionally, APEX addresses the risk of AI slop (low-quality AI outputs) by emphasizing the balance between innovation and system reliability. The framework is designed to be flexible, accommodating organizations at different stages of AI maturity, from experimentation to full integration, and stresses the need to align AI adoption with existing engineering cadences and organizational priorities. Ultimately, APEX aims to modernize workflows by ensuring AI enhances predictability, efficiency, and developer experience without compromising long-term stability or team well-being.

Recent Episodes of Dev Interrupted

24 Mar 2026 Why AI-assisted PRs merge at half the rate of human code | LinearBs 2026 Benchmarks

The 2026 Engineering Benchmark Report reveals that while 88.3% of developers use AI regularly, AI-generated pull requests face low merge rates (32.7%), larger sizes, and prolonged reviews due to systemic issues like poor data quality, inadequate policies, and organizational gaps, emphasizing the need for governance, smaller focused PRs, and foundational practices to optimize AI's potential in engineering workflows.

More Dev Interrupted episodes