<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[jucodes]]></title><description><![CDATA[jucodes]]></description><link>https://jucodes.dev</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1767856213108/93351700-4da0-48d2-966b-4bec8cc72287.png</url><title>jucodes</title><link>https://jucodes.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 00:21:16 GMT</lastBuildDate><atom:link href="https://jucodes.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[JuCodes: Engineering the Gap Between Backend & AI]]></title><description><![CDATA[I’ve been thinking about writing for a long time, but like many developers, I kept postponing it.
As a backend engineer, my days are usually spent in the "deterministic" world—where Input A should always lead to Output B. I build APIs, fix bugs, and ...]]></description><link>https://jucodes.dev/jucodes-engineering-the-gap-between-backend-and-ai</link><guid isPermaLink="true">https://jucodes.dev/jucodes-engineering-the-gap-between-backend-and-ai</guid><category><![CDATA[writing]]></category><category><![CDATA[Software Engineering]]></category><category><![CDATA[backend]]></category><category><![CDATA[#learning-in-public]]></category><dc:creator><![CDATA[juweria mohamood]]></dc:creator><pubDate>Sun, 08 Feb 2026 21:00:54 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/cckf4TsHAuw/upload/f1b3cc48f89a21393c9e273c75df98f5.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I’ve been thinking about writing for a long time, but like many developers, I kept postponing it.</p>
<p>As a backend engineer, my days are usually spent in the "deterministic" world—where Input A should always lead to Output B. I build APIs, fix bugs, and optimize cloud infrastructure. But lately, the industry has shifted. We aren't just building CRUD apps anymore; we are building <strong>Intelligent Systems.</strong></p>
<p>I realized that "later" never comes, so this is me starting—documenting my transition from a traditional backend developer to an <strong>AI Engineer.</strong></p>
<h3 id="heading-the-backend-of-ai"><strong>The Backend of AI</strong></h3>
<p>I primarily work with <strong>Python and JavaScript</strong>, but my focus has evolved. While I still love a clean PostgreSQL schema, I’m now spending more time thinking about:</p>
<ul>
<li><p><strong>Vector Databases &amp; RAG:</strong> How to give LLMs a "long-term memory" that actually scales.</p>
</li>
<li><p><strong>Agentic Workflows:</strong> Moving beyond simple prompts to autonomous agents that can execute tasks.</p>
</li>
<li><p><strong>LLMOps &amp; Deployment:</strong> Getting AI out of the playground and into production environments like AWS and DigitalOcean.</p>
</li>
</ul>
<p>I work full-time as a software engineer, so <strong>JuCodes</strong> isn't about pretending I have all the answers. It’s a "Build-in-Public" lab where I share the messy, non-deterministic parts of AI engineering that you won't find in a polished documentation page.</p>
<h3 id="heading-why-jucodes"><strong>Why JuCodes?</strong></h3>
<p>The "AI hype" is everywhere, but there is a massive gap between a cool demo and a production-ready AI feature. I created this space to bridge that gap.</p>
<p>Writing helps me:</p>
<ul>
<li><p><strong>Codify My Stack:</strong> Deep-diving into the tools (like Pinecone, LangChain, and Gemini) that I use every day.</p>
</li>
<li><p><strong>Solve for Reliability:</strong> Documenting how to handle AI hallucinations and latency in the backend.</p>
</li>
<li><p><strong>Share the "System" View:</strong> Focusing on the architecture, not just the prompt.</p>
</li>
</ul>
<h3 id="heading-what-ill-be-writing-about"><strong>What I’ll be writing about</strong></h3>
<p>On JuCodes, expect deep-dives into:</p>
<ul>
<li><p><strong>AI Orchestration:</strong> Using Python and Node.js to manage complex LLM chains.</p>
</li>
<li><p><strong>Production-Grade RAG:</strong> Strategies for data chunking, embeddings, and retrieval.</p>
</li>
<li><p><strong>DevOps for AI:</strong> Deploying and monitoring models in real-world environments.</p>
</li>
<li><p><strong>The AI Engineering Stack:</strong> Reviews of the tools and APIs that actually survive a stress test.</p>
</li>
</ul>
<h3 id="heading-who-this-is-for"><strong>Who this is for</strong></h3>
<p>This blog is for <strong>engineers, not just enthusiasts.</strong> If you are a backend-focused developer trying to figure out how to integrate AI into your existing stack without breaking everything, you’re in the right place. We focus on practical insights and real code over hype.</p>
<p>This is just the beginning. The goal is to build a useful corner of the internet for developers who care about <strong>engineering AI properly.</strong></p>
<p>If you’d like to follow along, feel free to bookmark the blog or follow me here on Hashnode.</p>
<p><strong>Welcome to JuCodes.</strong></p>
]]></content:encoded></item></channel></rss>