<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python on Tim Schaeps</title>
    <link>https://www.timschaeps.be/tags/python/</link>
    <description>Recent content in Python on Tim Schaeps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2010–2026, all rights reserved.</copyright>
    <lastBuildDate>Mon, 11 May 2026 16:00:00 +0200</lastBuildDate><atom:link href="https://www.timschaeps.be/tags/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My GitHub Copilot Journey - Part 8: Building the Dashboard</title>
      <link>https://www.timschaeps.be/post/github-copilot-journey-part-8-building-the-dashboard/</link>
      <pubDate>Mon, 11 May 2026 16:00:00 +0200</pubDate>
      
      <guid>https://www.timschaeps.be/post/github-copilot-journey-part-8-building-the-dashboard/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;What do you do when you&#39;ve been documenting your AI journey in blog posts, and you realize you want to &lt;em&gt;see&lt;/em&gt; the data, not just describe it?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You build a dashboard. Obviously. 😊&lt;/p&gt;
&lt;h2 id=&#34;the-itch&#34;&gt;The itch&lt;/h2&gt;
&lt;p&gt;Throughout this series, I&#39;ve been talking about phases, milestones, evolution. In &lt;a href=&#34;https://www.timschaeps.be/post/github-copilot-journey-part-7-fixing-a-big-issue/&#34;&gt;Part 7&lt;/a&gt;


 I even calculated ROI manually during a debugging session. But all of that was narrative. I kept thinking: what if I could just &lt;em&gt;run a command&lt;/em&gt; and see my entire journey laid out in front of me?&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>