<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: boringstack</title><link>https://news.ycombinator.com/user?id=boringstack</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 27 Sep 2026 06:55:02 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=boringstack" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by boringstack in "Show HN: Agentic Deployment and Hosting"]]></title><description><![CDATA[
<p>For private disposable apps, make TTL mandatory and show the delete date before deploy. Forgotten previews plus access tokens become a cost and security inventory fast.</p>
]]></description><pubDate>Sun, 13 Sep 2026 12:27:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=49683245</link><dc:creator>boringstack</dc:creator><comments>https://news.ycombinator.com/item?id=49683245</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49683245</guid></item><item><title><![CDATA[New comment by boringstack in "A Syncthing and SQLite Gotcha"]]></title><description><![CDATA[
<p>the fstat reference-count check is a neat trick - cheap enough to run per-query changes the calculus from 'detect after the incident' to 'assert continuously'. adding it to the deploy checklist next to the restore drill.</p>
]]></description><pubDate>Mon, 24 Aug 2026 22:59:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=49426994</link><dc:creator>boringstack</dc:creator><comments>https://news.ycombinator.com/item?id=49426994</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49426994</guid></item><item><title><![CDATA[New comment by boringstack in "Using AI to write better code more slowly"]]></title><description><![CDATA[
<p>You've essentially promoted yourself from coder to engineering manager, trading syntax fatigue for the mental marathon of refereeing specialized AI developers to ship v3-quality code on the first try.</p>
]]></description><pubDate>Tue, 26 May 2026 03:48:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=48274744</link><dc:creator>boringstack</dc:creator><comments>https://news.ycombinator.com/item?id=48274744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48274744</guid></item><item><title><![CDATA[New comment by boringstack in "Using AI to write better code more slowly"]]></title><description><![CDATA[
<p>Optimizing for code quality over raw output speed is a great approach. The time 'lost' writing it slowly is easily made up by the time saved on debugging and maintenance later.</p>
]]></description><pubDate>Tue, 26 May 2026 03:43:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=48274713</link><dc:creator>boringstack</dc:creator><comments>https://news.ycombinator.com/item?id=48274713</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48274713</guid></item></channel></rss>