<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tim Silver - Technical Architect &amp; Full-Stack Developer</title>
    <link>https://timsilver.dev</link>
    <description>Tim Silver is a technical architect and full-stack developer specialising in modern web systems, e-commerce platforms, and scalable application architecture.</description>
    <language>en-gb</language>
    <lastBuildDate>Fri, 05 Jun 2026 23:20:07 GMT</lastBuildDate>
    <atom:link href="https://timsilver.dev/rss.xml" rel="self" type="application/rss+xml"/>
    
    <item>
      <title>Built isn’t done: operability as a first‑class requirement</title>
      <link>https://timsilver.dev/blog/built-isnt-done-operability-as-a-firstclass-requirement</link>
      <guid isPermaLink="true">https://timsilver.dev/blog/built-isnt-done-operability-as-a-firstclass-requirement</guid>
      <description>Shipping code is the easy part. Keeping it running, debuggable, and supportable under real traffic is where projects either mature… or quietly bleed time. Here’s how I think about operability as a requirement, not an afterthought.</description>
      <pubDate>Fri, 10 Apr 2026 00:32:16 GMT</pubDate>
      <category>Systems that Ship</category>
      <category>Architecture</category>
      <category>Delivery</category>
      <category>Observability</category>
      <category>Reliability</category>
      <category>Operability</category>
      <category>Integrations</category>
    </item>
    <item>
      <title>One day at a time: milestones, momentum, and the line between leading and micromanaging</title>
      <link>https://timsilver.dev/blog/milestones-momentum-and-the-line-between-leading-and-micromanaging</link>
      <guid isPermaLink="true">https://timsilver.dev/blog/milestones-momentum-and-the-line-between-leading-and-micromanaging</guid>
      <description>Big projects don’t become late all at once - they slip “one day at a time”. When the deadline can’t move, milestone granularity stops being admin and starts being a control system: tight feedback loops, measurable daily outcomes, and a healthy balance between leading a team and micromanaging it. This is the approach I fall back on when sprints feel too long and progress starts to go soft around the edges.</description>
      <pubDate>Thu, 12 Mar 2026 01:48:33 GMT</pubDate>
      <category>Project Delivery</category>
      <category>Engineering Leadership</category>
      <category>Technical Architecture</category>
      <category>The Mythical Man-Month</category>
      <category>Execution &amp; Momentum</category>
    </item>
    <item>
      <title>Hello, world (again) - why I’m starting timsilver.dev</title>
      <link>https://timsilver.dev/blog/hello-world-again-why-im-starting-timsilverdev</link>
      <guid isPermaLink="true">https://timsilver.dev/blog/hello-world-again-why-im-starting-timsilverdev</guid>
      <description>I’ve been meaning to start this blog for ages - the kind of idea that comes back after a gnarly project, a messy incident, or a decision you know you’ll have to justify later. https://timsilver.dev is where I’ll write down what I’ve learned building and shipping real products: practical architecture, delivery risk, integrations, security, and the unglamorous details that decide whether things actually work.</description>
      <pubDate>Wed, 11 Mar 2026 02:41:58 GMT</pubDate>
      <category>Technical Architecture</category>
      <category>Engineering Leadership</category>
    </item>
  </channel>
</rss>