<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Obsidian on SQP Dev</title>
    <link>/tags/obsidian/</link>
    <description>Recent content in Obsidian on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/obsidian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pushing the Vault to TickTick — Closing the Loop Between Obsidian and Task Management</title>
      <link>/posts/2026-05-28-obsidian-ticktick-sync/</link>
      <pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-28-obsidian-ticktick-sync/</guid>
      <description>&lt;p&gt;The vault knows everything. It has the lesson schedule, the practice sessions, the quiz material. TickTick is where the day actually runs — it sits in the calendar, it sends reminders, it blocks time. For a while those two lived separately, and any reschedule meant updating both by hand.&lt;/p&gt;&#xA;&lt;p&gt;Today that gap is closed.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;&#xA;&lt;p&gt;Obsidian is the source of truth for the learning plan. But TickTick is what I actually look at during the day. When a lesson moved, I&amp;rsquo;d update the calendar note in Obsidian and then forget to touch TickTick. Or update TickTick and leave the vault behind. Either way, something was always out of sync.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building an AI-Powered Quiz Into the Learning Loop</title>
      <link>/posts/2026-05-27-ai-quiz-learning-loop/</link>
      <pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-27-ai-quiz-learning-loop/</guid>
      <description>&lt;p&gt;Answering questions in your own words is good for learning. Answering them by clicking a button is better than not answering them at all.&lt;/p&gt;&#xA;&lt;p&gt;That sounds like a low bar, but it&amp;rsquo;s actually the insight that shaped the quiz system. At 20:00 after a full day I&amp;rsquo;m not going to write paragraphs about container networking from memory. But I will click through ten multiple choice questions if the friction is low enough and the questions are good.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reclaim, Google Calendar, and the Morning Briefing Skill</title>
      <link>/posts/2026-05-26-reclaim-morning-briefing/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-26-reclaim-morning-briefing/</guid>
      <description>&lt;p&gt;The moment that changed the whole system was realising that Claude Code is a terrible calendar manager.&lt;/p&gt;&#xA;&lt;p&gt;Not because it can&amp;rsquo;t do it — it can. The Google Calendar MCP integration works, skills can create and update events, everything is technically possible. The problem is cost. Every calendar operation burns tokens. Reschedule five tasks and you&amp;rsquo;ve spent more on API calls than the Reclaim monthly subscription.&lt;/p&gt;&#xA;&lt;p&gt;So I made a clean decision: Claude Code never touches the calendar for scheduling. That&amp;rsquo;s Reclaim&amp;rsquo;s job.&lt;/p&gt;</description>
    </item>
    <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>
    <item>
      <title>TickTick, Todoist, Reclaim — Finding the Right Task Manager</title>
      <link>/posts/2026-05-24-ticktick-todoist-reclaim/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-24-ticktick-todoist-reclaim/</guid>
      <description>&lt;p&gt;Every learning system needs somewhere tasks live. I went through three tools in fairly quick succession, and each one taught me something useful.&lt;/p&gt;&#xA;&lt;h2 id=&#34;ticktick--the-comfortable-choice&#34;&gt;TickTick — The Comfortable Choice&lt;/h2&gt;&#xA;&lt;p&gt;I started with TickTick because I already knew it. Simple interface, good mobile app, doesn&amp;rsquo;t require an hour of setup to get started. For general life tasks it&amp;rsquo;s perfectly good.&lt;/p&gt;&#xA;&lt;p&gt;The problem was the edges. TickTick doesn&amp;rsquo;t connect naturally to Obsidian. There&amp;rsquo;s no clean way to link a task in TickTick to a note in Obsidian, and no way to query TickTick tasks from inside the vault. Every time I finished a lesson and wanted to log it, I was switching apps, copying information, doing the same thing twice.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Claude Code as a Vault Brain — First Steps</title>
      <link>/posts/2026-05-23-claude-code-vault-brain/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-23-claude-code-vault-brain/</guid>
      <description>&lt;p&gt;The DevOps Learning Command Center dashboard existed. The problem was keeping it alive.&lt;/p&gt;&#xA;&lt;p&gt;A learning system that requires manual maintenance eventually stops being maintained. I wanted Claude Code — the terminal-based AI agent from Anthropic — to handle the vault upkeep so I could focus on the actual learning.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-claude-code-does&#34;&gt;What Claude Code Does&lt;/h2&gt;&#xA;&lt;p&gt;Claude Code runs in your terminal and has direct access to your filesystem. It reads files, writes files, runs commands. Combined with a &lt;code&gt;CLAUDE.md&lt;/code&gt; context file that explains who you are and what the vault is for, it becomes something like a personal assistant that actually knows your project.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building a DevOps DevOps Learning Command Center in Obsidian</title>
      <link>/posts/2026-05-22-obsidian-command-center/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-22-obsidian-command-center/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m 56, learning DevOps from scratch, and I have a problem with tools.&lt;/p&gt;&#xA;&lt;p&gt;Not using them — I love tools. The problem is spending more time building the perfect learning environment than actually learning. It&amp;rsquo;s a trap I know well and fall into anyway.&lt;/p&gt;&#xA;&lt;p&gt;This time I decided to be deliberate about it. If I was going to build a system, it would be one that genuinely serves the learning — not just looks good in screenshots.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
