<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tech-Lead on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/tech-lead/</link>
    <description>Recent content in Tech-Lead on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 10 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/tech-lead/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Nobody Tells You About Being a Tech Lead</title>
      <link>https://www.secdev.uk/blog/leadership/2.2-what-nobody-tells-you-about-being-a-tech-lead/</link>
      <pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.2-what-nobody-tells-you-about-being-a-tech-lead/</guid>
      <description>&lt;p&gt;The tech lead role is one of the most misunderstood positions in engineering. It&amp;rsquo;s not a title, it&amp;rsquo;s a set of responsibilities. It&amp;rsquo;s not a promotion, it&amp;rsquo;s a lateral move into a fundamentally different kind of work. And it&amp;rsquo;s where most engineers first discover whether they enjoy leadership, or whether they&amp;rsquo;d rather stay deep in the code.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been a tech lead multiple times across my career, and I still think it&amp;rsquo;s the hardest role in engineering. Not because the problems are the most complex technically, but because you&amp;rsquo;re pulled in three directions simultaneously and nobody tells you how to balance them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
