<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developer-Experience on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/developer-experience/</link>
    <description>Recent content in Developer-Experience on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/developer-experience/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rethinking Developer Productivity in the Age of AI Assistants</title>
      <link>https://www.secdev.uk/blog/leadership/4.2-rethinking-developer-productivity/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.2-rethinking-developer-productivity/</guid>
      <description>&lt;p&gt;Lines of code per day was always a terrible productivity metric. With AI coding assistants, it&amp;rsquo;s become an absurd one. An engineer with Copilot or a similar tool can generate code at a pace that would have been unimaginable five years ago. If you&amp;rsquo;re measuring productivity by volume, every engineer just got a 3x raise. If you&amp;rsquo;re measuring it by value delivered, the picture is more complicated.&lt;/p&gt;&#xA;&lt;p&gt;The more I&amp;rsquo;ve explored how AI assistants change engineering workflows, the more I&amp;rsquo;ve realised that the productivity conversation needs a fundamental reset. We&amp;rsquo;re not just doing the same work faster, we&amp;rsquo;re changing what the work is.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
