<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Culture on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/culture/</link>
    <description>Recent content in Culture on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 02 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/culture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Culture Is What You Do When Things Go Wrong</title>
      <link>https://www.secdev.uk/blog/leadership/3.9-culture-is-what-you-do-when-things-go-wrong/</link>
      <pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.9-culture-is-what-you-do-when-things-go-wrong/</guid>
      <description>&lt;p&gt;Every company I&amp;rsquo;ve worked at had values written down somewhere. Integrity. Innovation. Collaboration. Respect. They were on the website, in the onboarding deck, sometimes literally on the walls. And in most cases, they told you almost nothing about what it was actually like to work there.&lt;/p&gt;&#xA;&lt;p&gt;Culture isn&amp;rsquo;t what you say you value. It&amp;rsquo;s what you do, especially when things go wrong. Ines Sombra puts it perfectly: &amp;ldquo;Culture is what happens when what we want to believe about ourselves is challenged. Culture is what we do when we get things wrong, when we witness a violation of trust, or when we stay silent when an inappropriate comment is said in our presence.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Brilliant Jerk Problem</title>
      <link>https://www.secdev.uk/blog/leadership/1.6-the-brilliant-jerk-problem/</link>
      <pubDate>Mon, 07 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/1.6-the-brilliant-jerk-problem/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a conversation that every engineering leader has at some point. It usually starts with something like: &amp;ldquo;Yeah, they&amp;rsquo;re difficult, but they&amp;rsquo;re the only person who understands the billing system.&amp;rdquo; Or: &amp;ldquo;I know people find them hard to work with, but their output is incredible.&amp;rdquo; You nod along, because you&amp;rsquo;ve probably said something similar yourself. I certainly have.&lt;/p&gt;&#xA;&lt;p&gt;The brilliant jerk problem is one of those leadership challenges that feels genuinely hard the first time you face it, and blindingly obvious in hindsight. Someone on your team produces exceptional technical work, maybe they&amp;rsquo;re the fastest coder, the one who understands the gnarliest parts of the system, the person who can debug anything. But they also make people feel small. They dismiss ideas with contempt. They create an atmosphere where others are afraid to speak up, ask questions, or challenge anything.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
