{
	"version": "https://jsonfeed.org/version/1.1",
	"title": "Samantha Maria Dawson-Banks",
	"language": "en",
	"home_page_url": "https://chip-mail.co.nz/",
	"feed_url": "https://chip-mail.co.nz/feed/feed.json",
	"description": "If a cluttered desk is a sign of a cluttered mind, then a desk full of half-finished projects reflects exploration in progress — welcome to my digital home for my professional, personal, and academic pursuits.",
	"author": {
		"name": "Samantha Maria Dawson-Banks",
		"url": "https://chip-mail.co.nz/about/"
	},
	"items": [
		{
			"id": "https://chip-mail.co.nz/blog/cooking-without-fear/",
			"url": "https://chip-mail.co.nz/blog/cooking-without-fear/",
			"title": "Cooking Without Fear: A Human-Centric System",
			"content_html": "<p>This project is a bit less &quot;tech&quot; but deeply &quot;human.&quot; I'm working on a <strong>cooking guide and system</strong> for people who find standard recipes overwhelming or stressful—specifically focusing on empowering those with ND/ASD/ADHD.</p>\n<h3 id=\"don-t-be-afraid-of-the-food\" tabindex=\"-1\">&quot;Don't Be Afraid of the Food&quot; <a class=\"header-anchor\" href=\"https://chip-mail.co.nz/blog/cooking-without-fear/\">#</a></h3>\n<p>The core philosophy is simple: promote food safety through clear guardrails while removing the anxiety and rigidity of traditional recipes.</p>\n<p>Many people are scared of &quot;doing it wrong,&quot; which leads to them avoiding cooking altogether. My goal is to build a system that:</p>\n<ul>\n<li>Provides clear safety boundaries.</li>\n<li>Encourages exploration and confidence.</li>\n<li>Removes the &quot;one right way&quot; pressure that standard recipes often impose.</li>\n</ul>\n<p>This project is a perfect example of my belief that powerful systems (whether in the kitchen or in the cloud) should reduce friction and make life easier for the people using them.</p>\n<p><em>I'll be sharing more on the design of this framework and the &quot;human architecture&quot; behind it soon.</em></p>\n",
			"date_published": "2026-04-21T00:00:00Z"
		}
		,
		{
			"id": "https://chip-mail.co.nz/blog/persistent-ai-workspaces/",
			"url": "https://chip-mail.co.nz/blog/persistent-ai-workspaces/",
			"title": "Persistent AI: Solving the LLM Context Problem",
			"content_html": "<p>I'm in the middle of creating a <strong>Docker image for self-deployed persistent agentic workspaces</strong>. If you've ever felt the &quot;do I need to tell you this again&quot; pain of working with LLMs, you know exactly why I'm building this.</p>\n<h3 id=\"the-problem\" tabindex=\"-1\">The Problem <a class=\"header-anchor\" href=\"https://chip-mail.co.nz/blog/persistent-ai-workspaces/\">#</a></h3>\n<p>Standard AI interfaces often treat each session as a clean slate, losing the deep context and nuanced history of a project. I'm using storage as a persistent context to ensure that my AI agents (like Gemini-CLI or Copilot-CLI) retain the information they need to be truly effective partners.</p>\n<h3 id=\"the-system\" tabindex=\"-1\">The System <a class=\"header-anchor\" href=\"https://chip-mail.co.nz/blog/persistent-ai-workspaces/\">#</a></h3>\n<p>I've already integrated this into a nightly auto CI/CD pipeline to a local repo. It's working to the point where:</p>\n<ul>\n<li>A new build and image redeploy doesn't impact my workflow.</li>\n<li>A <code>docker compose up --force-recreate</code> only results in about 15 seconds of downtime.</li>\n<li>I'm right back where I was, with full scroll-back and persistent context.</li>\n</ul>\n<p>This project leans into AI not just as a toy, but as a practical, enabling tool for developers and knowledge workers.</p>\n<p><em>Stay tuned for the architecture breakdown and Docker configurations.</em></p>\n",
			"date_published": "2026-04-20T00:00:00Z"
		}
		,
		{
			"id": "https://chip-mail.co.nz/blog/portable-linux-stem-drive/",
			"url": "https://chip-mail.co.nz/blog/portable-linux-stem-drive/",
			"title": "Portable Linux: The Raspberry Pi Stem Drive",
			"content_html": "<p>I'm currently reworking a <strong>Raspberry Pi Zero 2 W</strong> into a USB stem thumb drive. The goal is to create a &quot;carry anywhere&quot; low-power Linux environment that can be powered directly from a USB port.</p>\n<h3 id=\"the-vision\" tabindex=\"-1\">The Vision <a class=\"header-anchor\" href=\"https://chip-mail.co.nz/blog/portable-linux-stem-drive/\">#</a></h3>\n<p>A good tech worker shouldn't have to cart around a precious laptop to be productive. By configuring the Pi with:</p>\n<ul>\n<li><strong>Device-mode Ethernet</strong></li>\n<li><strong>SSH access</strong></li>\n<li><strong>Mass storage</strong></li>\n<li><strong>(Potentially) an e-ink display</strong></li>\n</ul>\n<p>I'm building a system that can be plugged into any host and immediately provide a familiar, secure development environment. It dovetails perfectly with my preference for thin-ish clients and flexible, accessible tech.</p>\n<p><em>More details on the hardware build and OS configuration coming soon.</em></p>\n",
			"date_published": "2026-04-19T00:00:00Z"
		}
		
	]
}