<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>LangChain on AI + Quant Engineering</title><link>https://miasyster.github.io/en/tags/langchain/</link><description>Recent content in LangChain on AI + Quant Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://miasyster.github.io/en/tags/langchain/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Didn't Use LangChain — The Design Logic Behind a Custom FSM Orchestration Engine</title><link>https://miasyster.github.io/en/posts/why-i-built-my-own-fsm-engine/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://miasyster.github.io/en/posts/why-i-built-my-own-fsm-engine/</guid><description>LangChain, LangGraph, CrewAI, PydanticAI — no shortage of AI orchestration frameworks. I evaluated all of them and built my own. Not NIH syndrome. When you need failure-mode-driven mutation strategies, phase-aware multi-model routing with different temperatures, and adaptive evolution based on trajectory analysis, the abstraction layers of general-purpose frameworks become obstacles to route around.</description></item></channel></rss>