<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: aykutseker</title><link>https://news.ycombinator.com/user?id=aykutseker</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 27 Apr 2026 15:44:35 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=aykutseker" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by aykutseker in "Ask HN: Can you tell the difference between Claude Sonnet and Opus?"]]></title><description><![CDATA[
<p>in short tasks they look identical and most people can't tell. opus shows its edge in long agent loops and 50k+ context, when sonnet starts dropping tool calls or rerunning steps. sonnet's fine for short stuff and the price is better. on longer agentic flows opus actually earns the cost in my experience.</p>
]]></description><pubDate>Mon, 27 Apr 2026 13:39:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=47921425</link><dc:creator>aykutseker</dc:creator><comments>https://news.ycombinator.com/item?id=47921425</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47921425</guid></item><item><title><![CDATA[New comment by aykutseker in "Agents Aren't Coworkers, Embed Them in Your Software"]]></title><description><![CDATA[
<p>yeah and the reconciliation pattern only really works when you can actually read current state. half of what agents do is side effects you can't observe. slack messages, payments, emails. agent times out, retries,customer gets billed twice. article kinda glosses over that.</p>
]]></description><pubDate>Sun, 26 Apr 2026 09:34:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47908843</link><dc:creator>aykutseker</dc:creator><comments>https://news.ycombinator.com/item?id=47908843</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47908843</guid></item><item><title><![CDATA[New comment by aykutseker in "What's missing in the 'agentic' story: a well-defined user agent role"]]></title><description><![CDATA[
<p>thanks, will try both.<p>if you've actually migrated an existing claude code setup to one of them, curious how the portability story worked. that's the part i'd been worried about.</p>
]]></description><pubDate>Sat, 25 Apr 2026 17:51:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=47903213</link><dc:creator>aykutseker</dc:creator><comments>https://news.ycombinator.com/item?id=47903213</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47903213</guid></item><item><title><![CDATA[New comment by aykutseker in "What's missing in the 'agentic' story: a well-defined user agent role"]]></title><description><![CDATA[
<p>been building on claude code for a while. the post's framing is right.<p>mcp gives you open standards on the tool layer but the harness 
(claude code, cursor) is still proprietary. your product is one 
anthropic decision away from breaking.<p>the user agent role the post calls for needs open harnesses, not just 
open standards. otherwise we end up rebuilding mobile under a new name.</p>
]]></description><pubDate>Sat, 25 Apr 2026 17:17:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=47902966</link><dc:creator>aykutseker</dc:creator><comments>https://news.ycombinator.com/item?id=47902966</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47902966</guid></item></channel></rss>