<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: eoncode</title><link>https://news.ycombinator.com/user?id=eoncode</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 07 Apr 2026 15:31:44 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=eoncode" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by eoncode in "Claude Code is being dumbed down?"]]></title><description><![CDATA[
<p>Sorry if this is just for giggles and doesn't add anything of value to the discussion, but I couldn't resist and asked Claude Sonnet 4.5 and Opus 4.6 to analyze the github issue that was opened.<p>Funnily enough, both independently sided with the users, not the authors.<p>The core problem: --verbose was repurposed instead of adding a new toggle. Users who relied on verbose for debugging (thinking, hooks, subagent output) now have broken workflows - to fix a UX decision that shouldn't have shipped as default in the first place.<p>What should have been done:<p><pre><code>  /config
  Show file paths: [on/off]
  Verbose mode: [on/off]  (unchanged)
</code></pre>
A simple separate toggle would've solved everything without breaking anyone's workflow.<p>Opus 4.6's parting thought: if you're building a developer tool powered by an AI that can reason about software design, maybe run your UX changes past it before shipping.<p>To be fair, your response explains the design philosophy well - longer trajectories, progressive disclosure, terminal constraints. All valid. But it still doesn't address the core point: why repurpose --verbose instead of adding a separate toggle? You can agree with the goal and still say the execution broke existing workflows.</p>
]]></description><pubDate>Thu, 12 Feb 2026 06:15:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=46985400</link><dc:creator>eoncode</dc:creator><comments>https://news.ycombinator.com/item?id=46985400</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46985400</guid></item><item><title><![CDATA[New comment by eoncode in "How we exploited CodeRabbit: From simple PR to RCE and write access on 1M repos"]]></title><description><![CDATA[
<p>for the author of the page, check the screenshot under "context is key", i think you missed censoring a public ip.</p>
]]></description><pubDate>Wed, 20 Aug 2025 11:52:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=44961007</link><dc:creator>eoncode</dc:creator><comments>https://news.ycombinator.com/item?id=44961007</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44961007</guid></item></channel></rss>