<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Large Language Models on Chen Kai Blog</title><link>https://www.chenk.top/en/categories/large-language-models/</link><description>Recent content in Large Language Models on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 19 Jan 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/categories/large-language-models/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Agents Complete Guide: From Theory to Industrial Practice</title><link>https://www.chenk.top/en/standalone/ai-agents-complete-guide/</link><pubDate>Mon, 19 Jan 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/standalone/ai-agents-complete-guide/</guid><description>&lt;p>A chatbot answers questions. An &lt;em>agent&lt;/em> gets things done — it browses, runs code, calls APIs, queries databases, and iterates until the job is complete. The same LLM powers both, but the wrapper differs: an agent runs in a loop with tools, memory, and the ability to inspect its own work.&lt;/p>
&lt;p>This guide is the expanded version of that idea. It covers the four core capabilities (planning, memory, tool use, reflection), major framework families, multi-agent collaboration, evaluation, and the production concerns that determine whether an agent succeeds or fails.&lt;/p></description></item><item><title>Prompt Engineering Complete Guide: From Zero to Advanced Optimization</title><link>https://www.chenk.top/en/standalone/prompt-engineering-complete-guide/</link><pubDate>Tue, 30 Sep 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/standalone/prompt-engineering-complete-guide/</guid><description>&lt;p>The same model, two prompts: one achieves 17% accuracy on grade-school math, the other 78%. The difference isn&amp;rsquo;t magic—it&amp;rsquo;s prompt engineering. This guide covers the techniques that work, the research behind them, and how to systematically optimize prompts for production.&lt;/p>
&lt;hr>
&lt;h2 id="what-you-will-learn" class="heading-anchor">What You Will Learn&lt;a href="#what-you-will-learn" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;ul>
&lt;li>&lt;strong>Foundations&lt;/strong> — zero-shot, few-shot, many-shot, task decomposition, and the five-block prompt skeleton.&lt;/li>
&lt;li>&lt;strong>Reasoning techniques&lt;/strong> — Chain-of-Thought, Self-Consistency, Tree of Thoughts, Graph of Thoughts, ReAct.&lt;/li>
&lt;li>&lt;strong>Automation&lt;/strong> — Automatic Prompt Engineering (APE), DSPy, LLMLingua compression.&lt;/li>
&lt;li>&lt;strong>Practical templates&lt;/strong> — structured output, code generation, data extraction, multi-turn chat.&lt;/li>
&lt;li>&lt;strong>Evaluation and debugging&lt;/strong> — metrics, A/B testing, error analysis, the failure-mode toolkit.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Prerequisites.&lt;/strong> Basic Python; experience calling any LLM API. No math background required.&lt;/p></description></item><item><title>LLM Workflows and Application Architecture: Enterprise Implementation Guide</title><link>https://www.chenk.top/en/standalone/llm-workflows-architecture/</link><pubDate>Thu, 31 Jul 2025 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/standalone/llm-workflows-architecture/</guid><description>&lt;p>Most LLM tutorials end where the interesting work begins. They show you how to call a chat completion endpoint, attach a vector store, and wrap the whole thing in a Streamlit demo. None of that is wrong, but none of it is what breaks at 3 a.m. when 10,000 users hit your service at once and every other answer is a hallucination.&lt;/p>
&lt;p>This article is about everything that comes after the demo. It is opinionated on purpose: production LLM systems are mostly plain distributed systems with one non-deterministic component bolted on, and most of the engineering effort goes into containing that non-determinism. We will work through seven dimensions — application architecture, workflow patterns, the RAG-vs-fine-tune decision, deployment topology, cost, observability, and enterprise integration — keeping each one short, concrete, and grounded in the levers that actually move the needle.&lt;/p></description></item></channel></rss>