<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure on Tim Schaeps</title>
    <link>https://www.timschaeps.be/tags/infrastructure/</link>
    <description>Recent content in Infrastructure on Tim Schaeps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2010–2026, all rights reserved.</copyright>
    <lastBuildDate>Thu, 30 Apr 2026 18:30:00 +0200</lastBuildDate><atom:link href="https://www.timschaeps.be/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My GitHub Copilot Journey - Part 7: Fixing a Big Issue (and What It Means)</title>
      <link>https://www.timschaeps.be/post/github-copilot-journey-part-7-fixing-a-big-issue/</link>
      <pubDate>Thu, 30 Apr 2026 18:30:00 +0200</pubDate>
      
      <guid>https://www.timschaeps.be/post/github-copilot-journey-part-7-fixing-a-big-issue/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;Today I had a deployment that was working yesterday. Today it wasn&#39;t. What followed was one of those debugging sessions that perfectly illustrates both the power and the economics of working with GitHub Copilot.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If you&#39;ve been following this series (starting with &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-1-the-first-ask/&#34;&gt;Part 1: The First Ask&lt;/a&gt;


), you know the progression: from quick questions, to deep conversations, to infrastructure automation, to multi-agent squads. This post is about what happens when that infrastructure &lt;em&gt;fights back&lt;/em&gt; — and how the tool helps you win. (And then, in a beautifully meta moment, I asked the tool to calculate its own cost. More on that later. 😊)&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>My GitHub Copilot Journey - Part 4: The Infrastructure Leap</title>
      <link>https://www.timschaeps.be/post/github-copilot-journey-part-4-the-infrastructure-leap/</link>
      <pubDate>Mon, 27 Apr 2026 22:30:00 +0200</pubDate>
      
      <guid>https://www.timschaeps.be/post/github-copilot-journey-part-4-the-infrastructure-leap/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;Eight weeks ago, I accidentally committed a secret to a public repository. Last week, I was designing authentication architectures with managed identities and federated credentials. Same person. Same tool. Completely different confidence level.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This post is about the most transformative phase of my journey: when I stopped using AI for code and content, and started using it for &lt;em&gt;infrastructure, deployment, and DevOps&lt;/em&gt;. To me, this is where the productivity gains went from impressive to structural. (I won&#39;t pretend the learning curve was smooth — there were definitely some embarrassing moments along the way.)&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>