<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software Development on Tim Schaeps</title>
    <link>https://www.timschaeps.be/tags/software-development/</link>
    <description>Recent content in Software Development on Tim Schaeps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2010–2026, all rights reserved.</copyright>
    <lastBuildDate>Mon, 27 Apr 2026 23:00:00 +0200</lastBuildDate><atom:link href="https://www.timschaeps.be/tags/software-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My GitHub Copilot Journey - Part 6: The Squad</title>
      <link>https://www.timschaeps.be/post/github-copilot-journey-part-6-the-squad/</link>
      <pubDate>Mon, 27 Apr 2026 23:00:00 +0200</pubDate>
      
      <guid>https://www.timschaeps.be/post/github-copilot-journey-part-6-the-squad/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-5-the-compound-effect/&#34;&gt;Part 5&lt;/a&gt;


, I described the compound effect — what happens when trust, depth, breadth, and infrastructure all stack up. I thought that was the end of the story. It wasn&#39;t.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Somewhere around week seven, I stopped talking to &lt;em&gt;one&lt;/em&gt; Copilot. I started assembling &lt;em&gt;squads&lt;/em&gt;. (I realize that sounds dramatic — but bear with me, it&#39;ll make sense in a moment 😊.)&lt;/p&gt;
&lt;p&gt;This is the part of the journey where GitHub Copilot stopped being a tool I used and became a system I orchestrated. Where I went from having one conversation at a time to coordinating multiple specialized agents working in parallel. And where I started thinking about how to bring this capability to an entire team — not just myself.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>My GitHub Copilot Journey - Part 5: The Compound Effect</title>
      <link>https://www.timschaeps.be/post/github-copilot-journey-part-5-the-compound-effect/</link>
      <pubDate>Mon, 27 Apr 2026 22:40:00 +0200</pubDate>
      
      <guid>https://www.timschaeps.be/post/github-copilot-journey-part-5-the-compound-effect/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;Two months ago, I asked an AI to explain an error message. Last week, I built a complete web application — frontend, backend, authentication, infrastructure, CI/CD pipeline, monitoring dashboards — in a single afternoon session of 122 exchanges.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is the final part of the series (well, almost — more on that in a moment). Not because the journey is over, but because the foundation is set. In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-1-the-first-ask/&#34;&gt;Part 1&lt;/a&gt;


 I built the reflex. In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-2-the-long-conversation/&#34;&gt;Part 2&lt;/a&gt;


 I went deep. In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-3-beyond-code/&#34;&gt;Part 3&lt;/a&gt;


 I went wide. In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-4-the-infrastructure-leap/&#34;&gt;Part 4&lt;/a&gt;


 I started automating the systems around my work. Part 5 is about what happens when all of those layers compound. (And yes, there&#39;s a &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-6-the-squad/&#34;&gt;Part 6&lt;/a&gt;


 — because the story didn&#39;t end where I expected.)&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>