<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ai-engineering on Rasik Jain - Senior Architect | Generative AI &amp; Full-Stack Engineering</title>
    <link>https://www.rasikjain.com/tags/ai-engineering/</link>
    <description>Recent content in ai-engineering on Rasik Jain - Senior Architect | Generative AI &amp; Full-Stack Engineering</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.rasikjain.com/tags/ai-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an LLM Application? Don&#39;t Skip the Guardrails Layer</title>
      <link>https://www.rasikjain.com/posts/building-llm-application-dont-skip-guardrails-layer/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.rasikjain.com/posts/building-llm-application-dont-skip-guardrails-layer/</guid>
      <description>When people talk about building LLM applications, the conversation usually starts with prompts.
If the responses aren&amp;rsquo;t good enough, we improve the prompt.
Then comes RAG and AI agents.
All of these matter. But there&amp;rsquo;s another layer that often gets overlooked:
Guardrails
Think about a code review.
Before code is merged into production, it gets reviewed. Not because developers write bad code, but because even experienced engineers miss edge cases or overlook security issues.</description>
    </item>
    
    <item>
      <title>Beyond Prompts: The Rise of AI Agent Memory</title>
      <link>https://www.rasikjain.com/posts/beyond-prompts-rise-of-ai-agent-memory/</link>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.rasikjain.com/posts/beyond-prompts-rise-of-ai-agent-memory/</guid>
      <description>For the past couple of years, the AI conversation has been all about prompt engineering. We experimented with different prompting techniques to get better responses from large language models.
But as AI agents become capable of handling more complex tasks, the challenge is no longer writing the perfect prompt. It&amp;rsquo;s helping the agent remember and plan.
Think about assigning an AI agent a task like researching competitors, creating a project plan, writing documentation, and tracking progress over several days.</description>
    </item>
    
    <item>
      <title>Agentic AI Is Quietly Becoming the New Software Architecture</title>
      <link>https://www.rasikjain.com/posts/agentic-ai-new-software-architecture/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.rasikjain.com/posts/agentic-ai-new-software-architecture/</guid>
      <description>Agentic AI is quietly becoming the new software architecture.
Not long ago, most GenAI apps were simple: prompt in, response out. Now, we are seeing something different: systems made up of multiple AI agents working together.
These agents can plan tasks, call APIs, retrieve data, and coordinate with other agents to complete workflows, with minimal human input.
A big shift for developers  Apps are becoming goal-driven instead of prompt-driven AI is moving into the application&amp;rsquo;s control flow Multi-agent systems are replacing single LLM pipelines Memory, planning, and tool-use are becoming core components  New engineering challenges But this also introduces a new set of engineering challenges:</description>
    </item>
    
  </channel>
</rss>
