<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Length Alone Hurts LLM Performance Despite Perfect Retrieval · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2510.05381/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2510.05381/feed.xml" rel="self" type="application/rss+xml" /><item><title>Context Length Alone Hurts LLM Performance Despite Perfect Retrieval — mentioned by cautiouscat</title><link>https://news.ycombinator.com/item?id=49170281</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.05381:49170281</guid><pubDate>Tue, 04 Aug 2026 15:23:45 GMT</pubDate><description>&lt;p&gt;IMO, these agentic guard rails aren&amp;#x27;t the answer. It seems like we&amp;#x27;re seeing that the more you stuff context, the more the agents forget and don&amp;#x27;t follow the guidelines.[1] Things like ArchUnit, static analyzers, and other deterministic tools can help with lower level things like architecture. For higher up stuff, I am increasingly feeling like agents don&amp;#x27;t guarantee anything and in many cases its just the opposite. This is where a thoughtful engineer and reviewer can keep things in check. It&amp;#x27;s possible I&amp;#x27;m off base here, but I can&amp;#x27;t make heads or tails of the LLM written readme. 1…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.05381/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
