<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>engineering-management on jk jensen</title><link>https://jkjensen.me/tags/engineering-management/</link><description>Recent content in engineering-management on jk jensen</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 30 Dec 2025 00:00:00 -0700</lastBuildDate><atom:link href="https://jkjensen.me/tags/engineering-management/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-Era Developer Metrics</title><link>https://jkjensen.me/posts/2025-12-30-ai-era-developer-metrics/</link><pubDate>Tue, 30 Dec 2025 00:00:00 -0700</pubDate><guid>https://jkjensen.me/posts/2025-12-30-ai-era-developer-metrics/</guid><description>For a decade, the DORA metrics were our North Star. They gave us a standardized way to measure the performance of software delivery teams: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery.
But the 2025 landscape looks different. With &amp;gt;90% of developers now using AI-assisted coding tools, our traditional metrics are starting to break.
The core issue is that DORA was designed for a world where code was expensive to write.</description></item></channel></rss>