<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>guardrails on Rasik Jain - Senior Architect | Generative AI &amp; Full-Stack Engineering</title>
    <link>https://www.rasikjain.com/tags/guardrails/</link>
    <description>Recent content in guardrails 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/guardrails/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>
    
  </channel>
</rss>
