<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Can Aha Moments Be Fake? Towards Quantifying Decorative and True Thinking in Chain-of-Thought · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2510.24941/</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.24941/feed.xml" rel="self" type="application/rss+xml" /><item><title>Can Aha Moments Be Fake? Towards Quantifying Decorative and True Thinking in Chain-of-Thought — mentioned by purplepatrick</title><link>https://news.ycombinator.com/item?id=49298531</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.24941:49298531</guid><pubDate>Fri, 14 Aug 2026 13:39:02 GMT</pubDate><description>&lt;p&gt;Yeah, basically everything that becomes context in a session will bias perception and communication style -- subagents, plan lingo, prompt lingo, etc. And then if you write a plan with the comms context having been biased, the lingo will creep into the plan, and from the plan into the code and code comments. And from there, bad lingo will go on multiplying like rabbits... I usually think of it in terms of having a &amp;quot;good&amp;quot; or &amp;quot;bad&amp;quot; session. In a bad session, there is a harmful bias that you can only get rid of through a new session. For example, if you exposed too much context about, say, a…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.24941/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
