<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Llm on bytemastermind's blog</title><link>https://bytemastermind.github.io/tags/llm/</link><description>Recent content in Llm on bytemastermind's blog</description><generator>Hugo</generator><language>en-us</language><copyright>© bytemastermind</copyright><lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bytemastermind.github.io/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>Delegate Work to LLMs Smartly</title><link>https://bytemastermind.github.io/posts/writeups/llm/pipellm/</link><pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate><guid>https://bytemastermind.github.io/posts/writeups/llm/pipellm/</guid><description>&lt;p>I work in a very specific field (Web Security), however I will try to generalize methods of how I work with LLMs to others, as the methodology should apply the same to all the fields. It&amp;rsquo;s important to mention that this method will NOT make the results &amp;ldquo;perfect&amp;rdquo;, however, it can significantly help you to get rid of most LLM hallucinations, and it aims to make the LLM strictly follow given steps. Also, it is not something that I would claim as &amp;ldquo;my original idea&amp;rdquo;. It is used by many, as it is something one naturally comes to if they want to get more trustworthy LLM results.&lt;/p></description></item></channel></rss>