<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Engineering on j0n-harr150n.com</title>
		<link>https://j0n-harr150n.com/categories/engineering/</link>
		<description>Recent content in Engineering on j0n-harr150n.com</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 12 Jul 2025 18:47:32 -0400</lastBuildDate>
		
			<atom:link href="https://j0n-harr150n.com/categories/engineering/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Navigating the Bleeding Edge: From Svelte 5 Struggles to a Resilient AI Development Playbook</title>
				<link>https://j0n-harr150n.com/engineering/svelte-5-struggles-with-ai/</link>
				<pubDate>Sat, 12 Jul 2025 18:47:32 -0400</pubDate>
				<guid>https://j0n-harr150n.com/engineering/svelte-5-struggles-with-ai/</guid>
				<description>&lt;h1 id=&#34;navigating-the-bleeding-edge-from-svelte-5-struggles-to-a-resilient-ai-development-playbook&#34;&gt;Navigating the Bleeding Edge: From Svelte 5 Struggles to a Resilient AI Development Playbook&lt;/h1&gt;&#xA;&lt;h2 id=&#34;when-ai-development-hits-a-wall&#34;&gt;When AI Development Hits a Wall&lt;/h2&gt;&#xA;&lt;p&gt;In my &lt;a href=&#34;https://j0n-harr150n.com/posts/beyond-the-productivity-boost/&#34;&gt;recent articles&lt;/a&gt;&#xA;, I&amp;rsquo;ve shared how &lt;strong&gt;Google Gemini&lt;/strong&gt; and &lt;strong&gt;Code Assist&lt;/strong&gt; transformed my development workflow. Building the Bug Hunter Toolkit in weeks, architecting complex features for &lt;strong&gt;The Shadow Cortex (TSC)&lt;/strong&gt; - AI felt like a superpower.&lt;/p&gt;&#xA;&lt;p&gt;Then reality hit. Hard.&lt;/p&gt;&#xA;&lt;p&gt;My latest deep dive into TSC&amp;rsquo;s development revealed a critical flaw in my AI collaboration approach. What started as a productivity boost became a debugging nightmare that nearly derailed weeks of progress.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
