<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: HeytalePazguato</title><link>https://news.ycombinator.com/user?id=HeytalePazguato</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 13 Jun 2026 04:07:47 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=HeytalePazguato" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by HeytalePazguato in "The revenge of the data scientist"]]></title><description><![CDATA[
<p>This matches what I've seen working with automated systems. The watching part is 
genuinely underrated. Evals give you a score. Watching gives you intuition about 
failure modes you didn't know to test for.<p>Sitting with a running system teaches you things you would never think to measure.</p>
]]></description><pubDate>Thu, 02 Apr 2026 02:24:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47609280</link><dc:creator>HeytalePazguato</dc:creator><comments>https://news.ycombinator.com/item?id=47609280</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47609280</guid></item><item><title><![CDATA[New comment by HeytalePazguato in "Slop is not necessarily the future"]]></title><description><![CDATA[
<p>The camps framing misses something. After 15 years writing code I've found the 
people who ship the best products understand both sides. You need to care about 
craft enough to know when AI output is garbage, and you need to care about 
shipping enough to not gold-plate things that don't matter.<p>The slop problem isn't AI, it's people who can't tell the difference between 
good and bad output because they never developed the craft in the first place. 
AI just makes that gap more visible.</p>
]]></description><pubDate>Wed, 01 Apr 2026 01:39:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=47595735</link><dc:creator>HeytalePazguato</dc:creator><comments>https://news.ycombinator.com/item?id=47595735</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47595735</guid></item><item><title><![CDATA[New comment by HeytalePazguato in "The Claude Code Source Leak: fake tools, frustration regexes, undercover mode"]]></title><description><![CDATA[
<p>The hooks system is the most underappreciated thing in what leaked. PreToolUse, 
PostToolUse, session lifecycle, all firing via curl to a local server. Clean 
enough to build real tooling on top of without fighting it.<p>The frustration regex is funny but honestly the right call. Running an LLM call 
just to detect "wtf" would be ridiculous.<p>KAIROS is what actually caught my attention. An always-on background agent that 
acts without prompting is a completely different thing from what Claude Code is 
today. The 15 second blocking budget tells me they actually thought through what 
it feels like to have something running in the background while you work, which 
is usually the part nobody gets right.</p>
]]></description><pubDate>Wed, 01 Apr 2026 01:29:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47595682</link><dc:creator>HeytalePazguato</dc:creator><comments>https://news.ycombinator.com/item?id=47595682</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47595682</guid></item></channel></rss>