<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fractional CTO on Lee Goldsworthy</title>
    <link>https://leegold.com/tags/fractional-cto/</link>
    <description>Recent content in Fractional CTO on Lee Goldsworthy</description>
    <generator>Hugo</generator>
    <language>en-au</language>
    <lastBuildDate>Tue, 01 Sep 2026 18:00:00 +0800</lastBuildDate>
    <atom:link href="https://leegold.com/tags/fractional-cto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>2026 is the year of feeling like you&#39;re falling behind</title>
      <link>https://leegold.com/posts/2026-is-the-year-of-feeling-like-youre-falling-behind/</link>
      <pubDate>Tue, 01 Sep 2026 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/2026-is-the-year-of-feeling-like-youre-falling-behind/</guid>
      <description>I&amp;rsquo;m calling it: 2026 is the year of Feeling Like You&amp;rsquo;re Falling Behind™.&#xA;&amp;ldquo;Who thinks they&amp;rsquo;re falling behind right now?&amp;rdquo; I asked on Thursday.&#xA;The room was comprised of tech folks: A mix of CTOs, VPs of Engineering, Founding Engineers, and Senior Engineers. They all had prior experience doing AI Engineering, yet every single one of them (including me) put their hand up.&#xA;The better question is &amp;ldquo;What are you going to do about it?</description>
    </item>
    <item>
      <title>Vibe coding is not vibe engineering</title>
      <link>https://leegold.com/posts/vibe-coding-is-not-vibe-engineering/</link>
      <pubDate>Tue, 05 May 2026 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/vibe-coding-is-not-vibe-engineering/</guid>
      <description>The Register&#xA;This isn&amp;rsquo;t a Technology story about the dangers of AI, this is a Risk Management story about the dangers of overconfidence.&#xA;For the last week, we&amp;rsquo;ve been inundated with hot takes about how &amp;ldquo;Claude deleted PocketOS production database&amp;rdquo;.&#xA;Of course Claude deleted their entire production database (or something similarly damaging), it was just a matter of time. The way this is being discussed misses the point entirely.</description>
    </item>
    <item>
      <title>How I run zero inbox as a Fractional</title>
      <link>https://leegold.com/posts/how-i-run-zero-inbox-as-a-fractional/</link>
      <pubDate>Mon, 24 Nov 2025 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/how-i-run-zero-inbox-as-a-fractional/</guid>
      <description>As a Fractional, my Attention Management has to be brutal, and a friend recently asked me to describe how I run my Zero Inbox.&#xA;it&amp;rsquo;s a blend of Eisenhower Matrices and recurring Ceremonies I use to manage the noise from working with 4-6 startups at a time (often with inboxes, calendars, chat and project tools for each), so I figured I&amp;rsquo;d share it here.&#xA;Core Principle: &amp;ldquo;I should only see things I need to do that Hour, that Day, or that Week (in that order), everything else should resurface at the right time without me thinking about it&amp;rdquo;</description>
    </item>
    <item>
      <title>A 30-second risk check before you click &#34;I accept&#34;</title>
      <link>https://leegold.com/posts/a-30-second-risk-check-before-you-click-i-accept/</link>
      <pubDate>Mon, 06 Oct 2025 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/a-30-second-risk-check-before-you-click-i-accept/</guid>
      <description>I get FOMO when looking at the promised productivity gains from all these amazing-looking new platforms I hear about every week (each bearing enticing promises of automating this or that generic administrative task), but I find myself regularly holding back from using them against the backdrop of not opening myself up to unreasonable security and privacy risk.&#xA;Here&amp;rsquo;s a practical example of how I did a 30 second risk sanity check for one I was about to try out earlier today that wanted access to my inbox, which is a big red flag for me:</description>
    </item>
    <item>
      <title>Curiosity is the job security</title>
      <link>https://leegold.com/posts/curiosity-is-the-job-security/</link>
      <pubDate>Mon, 30 Jun 2025 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/curiosity-is-the-job-security/</guid>
      <description>Your knowledge worker job will likely evolve significantly in the next 5 years. You&amp;rsquo;re probably fine if you&amp;rsquo;re the curious type who constantly experiments with your workflow. If not, I reckon you&amp;rsquo;ll struggle.&#xA;The most effective people I know are more productive now than ever, many leveraging LLMs. But their curious mindset would drive progress even if ChatGPT didn&amp;rsquo;t blast onto the scene in November 2022.&#xA;This echoes a core tenet of the agile frameworks: Continuous Improvement.</description>
    </item>
    <item>
      <title>From &#34;why are we doing this&#34; to &#34;how we measure success&#34;</title>
      <link>https://leegold.com/posts/from-why-are-we-doing-this-to-how-we-measure-success/</link>
      <pubDate>Tue, 25 Mar 2025 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/from-why-are-we-doing-this-to-how-we-measure-success/</guid>
      <description>There&amp;rsquo;s a progression in a Software Engineer&amp;rsquo;s career, but the job title doesn&amp;rsquo;t really help us to understand the broader journey.&#xA;Jnr/Mid SWE is about Applications and Infrastructure Snr/Staff SWE you add People and Delivery HoE/CTO you add Strategy, Culture and Risk&#xA;There&amp;rsquo;s a through-line in all of these, that grows in intensity through the progression:&#xA;As a Jnr/Mid, we learn to ask &amp;ldquo;Why are we doing this?&amp;rdquo;. You know, &amp;ldquo;Tell me about the problem we&amp;rsquo;re solving, or the benefit we&amp;rsquo;re hoping to get&amp;rdquo;.</description>
    </item>
    <item>
      <title>The $20k a month AWS bill with no revenue</title>
      <link>https://leegold.com/posts/the-20k-a-month-aws-bill-with-no-revenue/</link>
      <pubDate>Tue, 30 Jul 2024 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/the-20k-a-month-aws-bill-with-no-revenue/</guid>
      <description>&amp;ldquo;I had $20k/month in AWS bills and no revenue&amp;rdquo;&#xA;Do product engineering types have a responsibility to first time founders that goes beyond build and deploy, or is this a case of &amp;ldquo;It&amp;rsquo;s everyone&amp;rsquo;s right to set their own money on fire?&amp;rdquo;&#xA;I&amp;rsquo;m reflecting on how this year I&amp;rsquo;ve now seen seven examples of how entities within the Australian tech industry have happily taken significant sums (think $250k) from founders to build lavish MVPs, without feeling beholden to take even basic steps to check if the founder is ready to be building an MVP, like have they:</description>
    </item>
    <item>
      <title>Before you start your MVP</title>
      <link>https://leegold.com/posts/before-you-start-your-mvp/</link>
      <pubDate>Tue, 11 Jun 2024 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/before-you-start-your-mvp/</guid>
      <description>The Dream Link to heading You&amp;rsquo;ve worked in the field for 10 or 20 years, you&amp;rsquo;ve lived the problem first-hand, you&amp;rsquo;ve got this idea for a product. You know you won&amp;rsquo;t be a millionaire overnight, but your early revenues from the product will guide what features you build next. You just need to find &amp;ldquo;someone who knows tech&amp;rdquo;, and you&amp;rsquo;re ready to start building&amp;hellip;&#xA;&amp;hellip;is a fantasy we tell ourselves as founders.</description>
    </item>
    <item>
      <title>Non-tech leaders can effectively champion security</title>
      <link>https://leegold.com/posts/non-tech-leaders-champion-security/</link>
      <pubDate>Mon, 27 May 2024 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/non-tech-leaders-champion-security/</guid>
      <description>Park your car in a bad suburb, leave your laptop on the passenger seat, leave your keys in the ignition. What happens next?&#xA;The above is akin to what I often see in tech-enabled early-stage companies with respect to their security and privacy practices: Dangerous sh*t that&amp;rsquo;s going to result in loss and sadness if some changes to skills and awareness aren&amp;rsquo;t made.&#xA;Here&amp;rsquo;s a real-world example of what I consider to be some of the best &amp;ldquo;everyday security culture&amp;rdquo; being put into practice by a non-tech leader at one of my clients:</description>
    </item>
    <item>
      <title>AWS cost optimisation is like servicing a car</title>
      <link>https://leegold.com/posts/aws-bill-like-servicing-car/</link>
      <pubDate>Tue, 02 Apr 2024 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/aws-bill-like-servicing-car/</guid>
      <description>Shovel cash into the furnace that is AWS/Azure. It&amp;rsquo;s fine.&#xA;For a while at least.&#xA;Don&amp;rsquo;t do cost optimisation Link to heading I encourage early stage tech companies to not even think about their AWS/Azure bill until it reaches $10k/y. At that point, it wants a timeboxed 1 hour sanity check, with perhaps a few hours of tightening up unused services, then don&amp;rsquo;t look again until it reaches $20k.</description>
    </item>
    <item>
      <title>Real Full Stack Developer</title>
      <link>https://leegold.com/posts/real-full-stack-developer/</link>
      <pubDate>Fri, 26 Jan 2024 18:00:00 +0800</pubDate>
      <guid>https://leegold.com/posts/real-full-stack-developer/</guid>
      <description>Have you ever met a REAL &amp;ldquo;full stack developer&amp;rdquo;?&#xA;I have. Once. Just recently.&#xA;During job interviews for a client, one walked in and (to my surprise), had no distinguishing visual features (no unicorn wings or horn, not even a faint glow).&#xA;We explored the usual interview topics, but it only took one sentence for them to convince me they were the real deal. It was weird the preternatural calmness with which they shared how their current employer would sometimes ask them to head out to the warehouse and stack pallets when there were no others with a valid forklift license currently on shift.</description>
    </item>
  </channel>
</rss>
