<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai on HomelabPro Blog</title>
    <link>/tags/ai/</link>
    <description>Recent content in Ai on HomelabPro Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 04 May 2026 13:47:56 +0800</lastBuildDate><atom:link href="/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI in My HomeLab</title>
      <link>/posts/2026-05-04-ai-in-my-homelab/</link>
      <pubDate>Mon, 04 May 2026 13:47:56 +0800</pubDate>
      
      <guid>/posts/2026-05-04-ai-in-my-homelab/</guid>
      
      <description>&lt;iframe data-testid=&#34;embed-iframe&#34; style=&#34;border-radius:12px&#34; src=&#34;https://open.spotify.com/embed/episode/6jouNKx4seaflg5zaogbEy?utm_source=generator&#34; width=&#34;100%&#34; height=&#34;352&#34; frameBorder=&#34;0&#34; allowfullscreen=&#34;&#34; allow=&#34;autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture&#34; loading=&#34;lazy&#34;&gt;&lt;/iframe&gt;
&lt;p&gt;I&amp;rsquo;ve had a home lab in some form for about fifteen years now, and for most of that time the whole point was to break things in a safe space before breaking them somewhere that actually mattered. A few years ago it was purely a test bed: spin something up, watch it fall over, figure out why, repeat. Now it&amp;rsquo;s also where I ship personal projects on a weekend, where I run automations that message me on WhatsApp when my CPU spikes, and where I&amp;rsquo;m still figuring out exactly how much of the keyboard I&amp;rsquo;m willing to hand over to an AI. That last part is what this one is really about.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Claude vs GitHub Copilot in VS Code</title>
      <link>/posts/2026-04-21-claude-vs-github-copilot-in-vscode/</link>
      <pubDate>Tue, 21 Apr 2026 17:22:53 +1000</pubDate>
      
      <guid>/posts/2026-04-21-claude-vs-github-copilot-in-vscode/</guid>
      
      <description>&lt;iframe data-testid=&#34;embed-iframe&#34; style=&#34;border-radius:12px&#34; src=&#34;https://open.spotify.com/embed/episode/40jiCFIakTUJxpZAz5UAp1?utm_source=generator&#34; width=&#34;100%&#34; height=&#34;352&#34; frameBorder=&#34;0&#34; allowfullscreen=&#34;&#34; allow=&#34;autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture&#34; loading=&#34;lazy&#34;&gt;&lt;/iframe&gt;
&lt;p&gt;I&amp;rsquo;ve been asked a few times lately which AI tool I&amp;rsquo;d actually recommend for day-to-day coding work, and honestly the question itself is a bit of a trap. Everyone wants one winner. One tool that does everything, handles every task, earns its subscription fee on its own. And I get it: subscription fatigue is real, and nobody wants to be paying for three things when one should do the job. But the honest answer, at least from where I&amp;rsquo;m sitting, is that Claude and GitHub Copilot inside VS Code are good at genuinely different things, and the friction starts the moment you try to force either one of them to do the whole job.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>VADA – Veeam Architecture Diagram Assistant</title>
      <link>/posts/2026-04-18-vada-veeam-architecture-diagram-assistant/</link>
      <pubDate>Sat, 18 Apr 2026 15:58:50 +0800</pubDate>
      
      <guid>/posts/2026-04-18-vada-veeam-architecture-diagram-assistant/</guid>
      
      <description>&lt;iframe width=&#34;100%&#34; height=&#34;415&#34; src=&#34;https://www.youtube.com/embed/MvT5SV57Z1o&#34; title=&#34;VADA – Veeam Architecture Diagram Assistant&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen loading=&#34;lazy&#34;&gt;&lt;/iframe&gt;
&lt;p&gt;So this one&amp;rsquo;s been in my head for a while. Something I kept running into, whether it&amp;rsquo;s tenders, customer conversations, or just internal planning, is that someone always needs a diagram. Everyone has their tool of choice: Draw.io, Excalidraw, Visio, and none of them know anything about Veeam. You&amp;rsquo;re always starting from scratch, hunting for the right icons, trying to remember which components connect to what.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Using AI for More Than Coding</title>
      <link>/posts/2026-04-17-using-ai-for-more-than-coding/</link>
      <pubDate>Fri, 17 Apr 2026 16:29:00 +0800</pubDate>
      
      <guid>/posts/2026-04-17-using-ai-for-more-than-coding/</guid>
      
      <description>&lt;iframe data-testid=&#34;embed-iframe&#34; style=&#34;border-radius:12px&#34; src=&#34;https://open.spotify.com/embed/episode/7md1giuQkNNYXRotDQANYb?utm_source=generator&#34; width=&#34;100%&#34; height=&#34;352&#34; frameBorder=&#34;0&#34; allowfullscreen=&#34;&#34; allow=&#34;autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture&#34; loading=&#34;lazy&#34;&gt;&lt;/iframe&gt;
&lt;p&gt;I know, I know, you&amp;rsquo;re probably exhausted hearing about AI. It&amp;rsquo;s everywhere, it&amp;rsquo;s in every conversation, every product announcement, every LinkedIn post. But I want to talk about it anyway, because my experience with it has gotten genuinely interesting and maybe a little uncomfortable, and I think it&amp;rsquo;s worth sharing.&lt;/p&gt;
&lt;p&gt;I use AI every single day. It&amp;rsquo;s just part of the workflow now, Claude Code is open, Copilot is open, and I don&amp;rsquo;t really think twice about it anymore. That&amp;rsquo;s kind of the whole point of this post though. Because the question I&amp;rsquo;ve started asking myself isn&amp;rsquo;t &amp;ldquo;is AI impressive?&amp;rdquo;&amp;hellip;it absolutely is,the question is whether it&amp;rsquo;s actually making me work better, or whether it just makes me &lt;em&gt;feel&lt;/em&gt; faster. There&amp;rsquo;s a difference, and I&amp;rsquo;m not sure I&amp;rsquo;ve always been on the right side of it.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Advent Calendar Day 7: Utilizing Veeam Intelligence with VeeamONE</title>
      <link>/posts/2025-12-07-advent-day07/</link>
      <pubDate>Sun, 07 Dec 2025 07:00:00 +0800</pubDate>
      
      <guid>/posts/2025-12-07-advent-day07/</guid>
      
      <description>&lt;h2 id=&#34;advent-calendar-day-7-integrating-ai-intelligence-with-veeamone&#34;&gt;
  Advent Calendar Day 7: Integrating AI Intelligence with VeeamONE
  &lt;a class=&#34;anchor-head&#34; href=&#34;#advent-calendar-day-7-integrating-ai-intelligence-with-veeamone&#34; aria-label=&#34;Anchor link to this heading&#34;&gt;&lt;/a&gt;
&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Disclaimer:&lt;/strong&gt;
I&amp;rsquo;m not a professional developer, and this content is intended to demonstrate the &amp;ldquo;art of the possible&amp;rdquo; rather than serve as production-ready guidance. Use these features with caution, and test thoroughly in your environment before relying on them for critical tasks.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Welcome to Day 7 of our Veeam Blog Advent Calendar! Over the last few days, we have spent a lot of time in automation, creating PowerShell scripts and N8N workflows and really seeing the power of automation. Today, I&amp;rsquo;d like to switch gears a little bit—still on the automation front—but rather than us writing our own code, let&amp;rsquo;s take a look at Veeam Intelligence.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>