<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Career-Development on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/career-development/</link>
    <description>Recent content in Career-Development 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/career-development/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>The Art of the One-on-One: Beyond Status Updates</title>
      <link>https://www.secdev.uk/blog/leadership/1.2-the-art-of-the-one-on-one-beyond-status-updates/</link>
      <pubDate>Mon, 15 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/1.2-the-art-of-the-one-on-one-beyond-status-updates/</guid>
      <description>&lt;p&gt;In the first article in this series, I wrote about psychological safety, the foundation that makes everything else in leadership possible. If there&amp;rsquo;s one place where that foundation gets tested every single week, it&amp;rsquo;s the one-on-one.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ll be honest: my early one-on-ones were terrible. I&amp;rsquo;d sit down with a report, open Jira, and essentially run a standup for two people. &amp;ldquo;How&amp;rsquo;s the migration going? Any blockers? Cool, see you next week.&amp;rdquo; I thought I was being efficient. What I was actually doing was wasting the most valuable recurring meeting on my calendar, and probably theirs too.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
