<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on SQP Dev</title>
    <link>/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Structuring the Vault Around a Real Learning Plan</title>
      <link>/posts/2026-05-25-vault-structure-learning-plan/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-25-vault-structure-learning-plan/</guid>
      <description>&lt;p&gt;Once the task manager question was settled, I could focus on what the vault actually needed to contain.&lt;/p&gt;&#xA;&lt;p&gt;The goal was simple: every Docker and Kubernetes lesson should have a home in the vault before I watch it, a note created during it, and a review scheduled after it. No manual steps, no decisions to make in the moment.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-learning-plan-structure&#34;&gt;The Learning Plan Structure&lt;/h2&gt;&#xA;&lt;p&gt;The Udemy course has 26 lessons spread across Docker and Kubernetes. I mapped them to a 5-week calendar: two sessions per day this week at 09:30 and 11:00, then one session per day at 06:35 from June onwards when I shift to an earlier schedule.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
