<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: advertum</title><link>https://news.ycombinator.com/user?id=advertum</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 07:58:56 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=advertum" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by advertum in "Show HN: Lightweight Task queue on Erlang/OTP, SQLite-backed, no overengineering"]]></title><description><![CDATA[
<p>Using the Redis Streams wire protocol means any existing Redis client works without changes. The queue is stored on disk, so tasks survive a restart. No new client library to add. One question: if a worker stops in the middle of a task, does the message go back to the queue for another worker?</p>
]]></description><pubDate>Sun, 14 Jun 2026 07:54:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=48525132</link><dc:creator>advertum</dc:creator><comments>https://news.ycombinator.com/item?id=48525132</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48525132</guid></item><item><title><![CDATA[New comment by advertum in "Harness engineering: Leveraging Codex in an agent-first world"]]></title><description><![CDATA[
<p>LOC was never really the point, if anything it's often the opposite. Being able to say the same thing more concisely makes code cheaper to maintain and easier to understand. (Not always: sometimes people are concise just for its own sake, and that's worse.) Either way, that whole debate feels like the past now.<p>As for metrics based on how much was produced or spent, like companies measuring developer performance by tokens used, that's a dead end regardless. Performance should be measured by outcomes: incident/failure rate, SLA, user numbers and feedback, revenue, that kind of thing.</p>
]]></description><pubDate>Mon, 08 Jun 2026 05:52:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=48441744</link><dc:creator>advertum</dc:creator><comments>https://news.ycombinator.com/item?id=48441744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48441744</guid></item><item><title><![CDATA[New comment by advertum in "pg_durable: Microsoft open sources in-database durable execution"]]></title><description><![CDATA[
<p>Agreed, but I think the hard part is the syntax, not the idea. The concept is simple. The way the SQL is written here is unusual, and since there is little training data on it, a model will likely fall back on a more common approach it has seen before.</p>
]]></description><pubDate>Sat, 06 Jun 2026 15:42:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=48426084</link><dc:creator>advertum</dc:creator><comments>https://news.ycombinator.com/item?id=48426084</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48426084</guid></item></channel></rss>