<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: kirBurkhanov</title><link>https://news.ycombinator.com/user?id=kirBurkhanov</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 26 Oct 2026 12:55:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=kirBurkhanov" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by kirBurkhanov in "The State of Context Engineering"]]></title><description><![CDATA[
<p>That calls lost-in-middle issue with LLM models. You have to use appropriate workflow patterns like map/reduce to handle big context. But be sure to run experiments on dataset first to understand what logic works well and stable. Where NOT! And how it can be combined to reduce LLM stohastic problems in prod</p>
]]></description><pubDate>Mon, 26 Oct 2026 09:18:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=50241163</link><dc:creator>kirBurkhanov</dc:creator><comments>https://news.ycombinator.com/item?id=50241163</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50241163</guid></item><item><title><![CDATA[New comment by kirBurkhanov in "SlopCodeBench 10/2026 – Opus 5.5, Astra wins overall, xhigh considered harmful"]]></title><description><![CDATA[
<p>Yeah, and the noise is also per model, run the same model five or ten times and put the confidence around it. Then try different models and different workflows. Thats actually how I do it when I build workflows and automations: test, test, and test, collect the statistic on where and what works better, then combine.</p>
]]></description><pubDate>Wed, 21 Oct 2026 09:48:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=50178181</link><dc:creator>kirBurkhanov</dc:creator><comments>https://news.ycombinator.com/item?id=50178181</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50178181</guid></item></channel></rss>