<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: sandbar</title><link>https://news.ycombinator.com/user?id=sandbar</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 16 Jun 2026 18:51:01 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=sandbar" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by sandbar in "Debugging: Indispensable rules for finding even the most elusive problems (2004)"]]></title><description><![CDATA[
<p>Take the time to speed up my iteration cycles has always been incredibly valuable. It can be really painful because its not directly contributing to determining/fixing the bug (which could be exacerbated if there is external pressure), but its <i>always</i> been worth it. Of course, this only applies to instances where it takes ~4+ minutes to run a single 'experiment' (test, startup etc). I find when I do just try to push through with long running tests I'll often forget the exact variable I tweaked during the course of the run. Further, these tweaks can be very nuanced and require you to maintain a lot of the larger system in your head.</p>
]]></description><pubDate>Mon, 13 Jan 2025 17:55:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=42686297</link><dc:creator>sandbar</dc:creator><comments>https://news.ycombinator.com/item?id=42686297</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42686297</guid></item></channel></rss>