<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/ai/</link>
    <description>Recent content in Ai on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The New Shape of the Engineering Team</title>
      <link>https://www.secdev.uk/blog/leadership/4.3-the-new-shape-of-the-engineering-team/</link>
      <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.3-the-new-shape-of-the-engineering-team/</guid>
      <description>&lt;p&gt;If AI can handle the boilerplate, the scaffolding, and a growing portion of routine implementation, what does that mean for how we compose engineering teams? It&amp;rsquo;s a question I&amp;rsquo;ve been turning over for a while now, and the answers I keep arriving at are uncomfortable.&lt;/p&gt;&#xA;&lt;p&gt;The optimistic version is that AI frees engineers to focus on higher-value work, system design, problem framing, user understanding, architectural thinking. The pessimistic version is that it eliminates the entry-level work that junior engineers have traditionally used to learn the craft. The realistic version is probably somewhere in between, and navigating it well is one of the most important challenges facing technical leaders right now.&lt;/p&gt;</description>
    </item>
    <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>
    <item>
      <title>The AI Literacy Gap: Why Your Leadership Team Needs to Catch Up</title>
      <link>https://www.secdev.uk/blog/leadership/4.1-the-ai-literacy-gap/</link>
      <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.1-the-ai-literacy-gap/</guid>
      <description>&lt;p&gt;With the emergance of AI/GenAI, I felt that I needed to think, and write, about the impact of AI/GenAI on technology leadership. The next series of articles will be exporing this topic. As an emerging topic, these articles may well be shorter, and I will try and publish them weekly when possible.&lt;/p&gt;&#xA;&lt;p&gt;Most engineering leadership teams I talk to have a wide spread of AI understanding. On one end, you&amp;rsquo;ve got the enthusiasts, they&amp;rsquo;ve built agents, they use AI coding assistants daily, they can explain transformer architectures over a pint. On the other end, you&amp;rsquo;ve got leaders who haven&amp;rsquo;t meaningfully engaged with any of it. They&amp;rsquo;ve read the headlines, they&amp;rsquo;ve sat through a vendor demo, and they&amp;rsquo;re quietly hoping this is a hype cycle that will pass.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
