<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://nishantnepal.github.io/</id><title>Build. Break. Learn.</title><subtitle>Building with AI, data, and cloud technologies</subtitle> <updated>2026-02-01T12:08:31-05:00</updated> <author> <name>Nishant Nepal</name> <uri>https://nishantnepal.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://nishantnepal.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://nishantnepal.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Nishant Nepal </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Azure Model Router</title><link href="https://nishantnepal.github.io/posts/gen-ai-azure-model-router/" rel="alternate" type="text/html" title="Azure Model Router" /><published>2026-01-04T00:00:00-05:00</published> <updated>2026-01-04T00:00:00-05:00</updated> <id>https://nishantnepal.github.io/posts/gen-ai-azure-model-router/</id> <content type="text/html" src="https://nishantnepal.github.io/posts/gen-ai-azure-model-router/" /> <author> <name>Nishant Nepal</name> </author> <category term="Generative AI" /> <category term="Azure" /> <summary>Intro When you are building Gen AI applications where the users are not interacting with the model (backend agentic AI applications or triggering a LLM through api), then you are more or less starting out with a single backend LLM that is the best fit for your call and as your code stabilizes, you upgrade the LLM depending on your evaluation criterias. Standard stuff. But, what happens if you...</summary> </entry> <entry><title>Agentic AI - Content Safety</title><link href="https://nishantnepal.github.io/posts/building-gen-ai-content-safety/" rel="alternate" type="text/html" title="Agentic AI - Content Safety" /><published>2025-12-26T00:00:00-05:00</published> <updated>2025-12-26T12:12:17-05:00</updated> <id>https://nishantnepal.github.io/posts/building-gen-ai-content-safety/</id> <content type="text/html" src="https://nishantnepal.github.io/posts/building-gen-ai-content-safety/" /> <author> <name>Nishant Nepal</name> </author> <category term="Generative AI" /> <category term="Architectural Concerns" /> <summary>Intro When building generative AI applications—especially customer-facing ones like chatbots—content safety aren’t optional. They’re essential. Large language models (LLMs) are powerful, but they’re also unpredictable. They can generate text, images, and even code in ways that are difficult to fully control. That means it’s not enough for an AI system to simply produce the right answer. It als...</summary> </entry> <entry><title>Linking MLFlow to Databricks Hosted</title><link href="https://nishantnepal.github.io/posts/data-eng-databricks-mlflow/" rel="alternate" type="text/html" title="Linking MLFlow to Databricks Hosted" /><published>2025-12-09T00:00:00-05:00</published> <updated>2025-12-09T09:46:07-05:00</updated> <id>https://nishantnepal.github.io/posts/data-eng-databricks-mlflow/</id> <content type="text/html" src="https://nishantnepal.github.io/posts/data-eng-databricks-mlflow/" /> <author> <name>Nishant Nepal</name> </author> <category term="Data Engineering" /> <category term="Databricks" /> <summary>This is a quick note to myself for future use cases. Often times, when devloping locally, i tend to point to a local MLFlow instance and then when deploying to upper environments, its redirected to a Databricks hosted MLFlow endpoint. For the most part this is fairly straightforward and databricks has good documentation here. For a quick verification test, here is my sample code import async...</summary> </entry> <entry><title>Agentic AI - Feedback</title><link href="https://nishantnepal.github.io/posts/building-gen-ai-feedback/" rel="alternate" type="text/html" title="Agentic AI - Feedback" /><published>2025-12-03T00:00:00-05:00</published> <updated>2025-12-09T08:46:20-05:00</updated> <id>https://nishantnepal.github.io/posts/building-gen-ai-feedback/</id> <content type="text/html" src="https://nishantnepal.github.io/posts/building-gen-ai-feedback/" /> <author> <name>Nishant Nepal</name> </author> <category term="Generative AI" /> <category term="Architectural Concerns" /> <summary>Intro Building generative AI applications introduces unique challenges—challenges we didn’t have to think about when building regular, non-AI software applications (remember those? 🙂). One challenge is feedback - whether it’s a user flagging a response as factually incorrect or an automated agent scanning and triaging issues, feedback is critical because it’s the only mechanism that closes the ...</summary> </entry> <entry><title>Agentic AI - Evaluations</title><link href="https://nishantnepal.github.io/posts/building-gen-ai-evaluation/" rel="alternate" type="text/html" title="Agentic AI - Evaluations" /><published>2025-11-12T00:00:00-05:00</published> <updated>2025-12-15T08:29:33-05:00</updated> <id>https://nishantnepal.github.io/posts/building-gen-ai-evaluation/</id> <content type="text/html" src="https://nishantnepal.github.io/posts/building-gen-ai-evaluation/" /> <author> <name>Nishant Nepal</name> </author> <category term="Generative AI" /> <category term="Architectural Concerns" /> <summary>Intro My career has fluctuated between software and data as primary focus areas, with infrastructure and DevSecOps as secondary strengths. While there may be more formal definitions of LLM evaluations, the one that resonates most with me is that it’s essentially software testing for AI models. In software testing—unit, integration, performance, etc.—we verify that deterministic code behaves as...</summary> </entry> </feed>
