<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Speed on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/speed/</link><description>Recent content in Speed on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 11 May 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/speed/index.xml" rel="self" type="application/rss+xml"/><item><title>Is AI raising your team's bar?</title><link>https://drlongnecker.com/blog/2026/05/ai-raises-the-bar-speed-value-comprehension/</link><pubDate>Mon, 11 May 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/05/ai-raises-the-bar-speed-value-comprehension/</guid><description>&lt;p&gt;In the past few years, generating code got faster, but understanding the problem well enough to generate the &lt;em&gt;right&lt;/em&gt; code didn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.devoteam.com/cz/expert-view/the-big-talking-point-in-product-development-speed-vs-value/"&gt;Speed went up along with rejected pull requests.&lt;/a&gt; More output, but more rework with it, widening the distance between what the business needed and what got built. The velocity metrics still look fine. The value metrics, where teams are measuring them at all, tell a different story.&lt;/p&gt;
&lt;!-- more --&gt;
&lt;p&gt;The pattern is consistent enough to be worth naming clearly. &lt;strong&gt;AI is an amplifier.&lt;/strong&gt; It accelerates what was already working; however, it also accelerates what wasn&amp;rsquo;t, which means imprecise requirements and missing guardrails produce consequences faster than they used to. The teams pulling ahead have figured that out. The ones still struggling are treating AI adoption primarily as a speed problem.&lt;/p&gt;</description></item></channel></rss>