<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: dezsirazvan</title><link>https://news.ycombinator.com/user?id=dezsirazvan</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 13 Jun 2026 00:56:07 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=dezsirazvan" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Ask HN: How do you handle "what did user X do yesterday" from customer support?]]></title><description><![CDATA[
<p>At my last three Rails jobs, customer support would ping engineering 5 times a day asking what a specific user did. An engineer would stop, grep prod logs, scroll past SQL, write back a one-sentence summary. Twenty minutes round trip each time.<p>I'm curious how other engineering teams handle this. Have you built something internal? Bought a tool? Just absorb the interruption cost and move on? Is there a pattern for the engineer-as-translator role on your team?<p>(For context, I ended up building https://ezlogs.io to handle this for myself, but I'm more curious about how other teams have solved or not solved it.)</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48449280">https://news.ycombinator.com/item?id=48449280</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 08 Jun 2026 18:27:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=48449280</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48449280</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48449280</guid></item><item><title><![CDATA[New comment by dezsirazvan in "Show HN: Tired of duct-taping access control into agent prompts. Here's the fix"]]></title><description><![CDATA[
<p>the read-only-by-default angle is underrated. been building an activity-log layer for agents and the moment we considered exposing write tools through MCP the security review story exploded. kept it query-only and integration went from "needs a security architecture doc" to "install the agent, done." most of the value of giving agents access to a system is just letting them read - the write part can usually go through whatever ops tooling already exists.</p>
]]></description><pubDate>Fri, 05 Jun 2026 11:56:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=48411192</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48411192</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48411192</guid></item><item><title><![CDATA[New comment by dezsirazvan in "The Slack message I built EZLogs to kill"]]></title><description><![CDATA[
<p>Founder here. A few things worth surfacing up front since it's been ~10 minutes:<p>The pitch is small. It's a Rails activity log gem that joins HTTP + Sidekiq + ActiveRecord into one card per user action. Not metrics, not APM, doesn't replace Datadog. The audience for the card is the rest of your company, not engineers.<p>The post above is the boring lesson from week one of having real users — the install template had a placeholder URL on launch day, and that placeholder cost me my first conversion. 0.1.8 is on RubyGems with the fix (pre-filled SaaS URL, reads the API key from ENV, one env var to set).<p>Happy to answer specifics: how correlation works across `perform_later` job boundaries without thread-locals, why MCP is unlimited at every paid tier (data-only, the customer's own AI narrates), what "read-only by design" rules out and why.</p>
]]></description><pubDate>Mon, 01 Jun 2026 11:15:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=48355318</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48355318</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48355318</guid></item><item><title><![CDATA[The Slack message I built EZLogs to kill]]></title><description><![CDATA[
<p>Article URL: <a href="https://ezlogs.io/blog/the-slack-message-i-built-this-to-kill/">https://ezlogs.io/blog/the-slack-message-i-built-this-to-kill/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48355239">https://news.ycombinator.com/item?id=48355239</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 01 Jun 2026 11:04:31 +0000</pubDate><link>https://ezlogs.io/blog/the-slack-message-i-built-this-to-kill/</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48355239</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48355239</guid></item><item><title><![CDATA[EZLogs: Plain-English activity logs for Rails and Next.js apps]]></title><description><![CDATA[
<p>Article URL: <a href="https://ezlogs.io/">https://ezlogs.io/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48321021">https://news.ycombinator.com/item?id=48321021</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 29 May 2026 09:40:12 +0000</pubDate><link>https://ezlogs.io/</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48321021</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48321021</guid></item><item><title><![CDATA[New comment by dezsirazvan in "YouTube to automatically label AI-generated videos"]]></title><description><![CDATA[
<p>good</p>
]]></description><pubDate>Thu, 28 May 2026 20:17:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=48314838</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48314838</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48314838</guid></item><item><title><![CDATA[New comment by dezsirazvan in "Claude Opus 4.8"]]></title><description><![CDATA[
<p>same!</p>
]]></description><pubDate>Thu, 28 May 2026 20:12:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=48314770</link><dc:creator>dezsirazvan</dc:creator><comments>https://news.ycombinator.com/item?id=48314770</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48314770</guid></item></channel></rss>