<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: netz00</title><link>https://news.ycombinator.com/user?id=netz00</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 17 Aug 2026 09:37:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=netz00" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by netz00 in "The Private Messenger That's Simple"]]></title><description><![CDATA[
<p>What is purpose of private messenger if your OS (Android) and hardware is likely compromised.</p>
]]></description><pubDate>Sun, 16 Aug 2026 14:23:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=49320382</link><dc:creator>netz00</dc:creator><comments>https://news.ycombinator.com/item?id=49320382</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49320382</guid></item><item><title><![CDATA[New comment by netz00 in "Vaultwarden Sequence Diagrams"]]></title><description><![CDATA[
<p>So many problems, beautifully entangled and solved together.<p>I prefer KeePass: it does one thing and does it well. Sharing passwords across multiple devices was never really a problem for KeePass itself to solve, but rather something that can be handled by software specialized for that purpose. Great example of good architecture!</p>
]]></description><pubDate>Sun, 16 Aug 2026 12:32:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=49319465</link><dc:creator>netz00</dc:creator><comments>https://news.ycombinator.com/item?id=49319465</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49319465</guid></item><item><title><![CDATA[New comment by netz00 in "AI Isn't Outthinking Mathematicians. It's Out-Remembering Them"]]></title><description><![CDATA[
<p>If and only if that is actually true, then perhaps nothing matters. Until then, calling out shenanigans remains a noble art.</p>
]]></description><pubDate>Sat, 15 Aug 2026 18:36:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=49313093</link><dc:creator>netz00</dc:creator><comments>https://news.ycombinator.com/item?id=49313093</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49313093</guid></item><item><title><![CDATA[New comment by netz00 in "Your Estimate Isn't Off Because of Optimism or Inexperience"]]></title><description><![CDATA[
<p>Isn’t an estimate supposed to be off?<p>The real question is: how much effort is worth spending to make it less wrong?<p>Improving an estimate has a cost, and sometimes it’s more efficient to accept being more off rather than spending disproportionate effort reducing the error.<p>Accuracy is useful when the cost of being wrong is high. But sometimes the cost of estimating accurately is higher than the cost of being wrong.</p>
]]></description><pubDate>Sat, 15 Aug 2026 14:09:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=49310731</link><dc:creator>netz00</dc:creator><comments>https://news.ycombinator.com/item?id=49310731</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49310731</guid></item><item><title><![CDATA[New comment by netz00 in "AI makes weak engineers less harmful"]]></title><description><![CDATA[
<p>I have the opposite experience. AI hasn't made weak engineers less harmful. It has made their output more plausible, which can make it more expensive to deal with.<p>I now spend a lot of time arguing with "meat proxies": someone submits an MR they don't understand, I find the subtle problems, explain them, and they copy-paste my response into Claude and get the work done. The work is effectively delegated to the reviewer, while "Bob" who the manager loves, gets to look like the efficient, promotion-ready engineer. So far, my solution has been to put in roughly the same amount of effort as before AI, then leave a comment saying that there may be more work required, but the review has already consumed enough budget and I'm approving it. Bounce the responsibility back and move on.<p>Same with ticket refinement: AI can turn a flawed/underspecified idea into a polished-looking ticket with hidden assumptions and scope creep. The problems only become apparent when you start implementing it, at which point you're asked why you didn't catch them before estimation. The best mitigation I've found is to leave questions for the author, but then we're back in the you ↔ meat proxy ↔ LLM loop, where you're effectively doing someone else's work.<p>Previously, weak output was often obvious. Now I find myself spending more time auditing plausible-looking output and communicating with an LLM through someone who doesn't understand the problem.<p>Solution? Currently none. Folks who don't want to do a job finally got a way to not do it. Until there is a clear incentive for them to actually do the work, they can keep offending their colleagues' intelligence with this behavior.</p>
]]></description><pubDate>Sat, 15 Aug 2026 12:04:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=49309913</link><dc:creator>netz00</dc:creator><comments>https://news.ycombinator.com/item?id=49309913</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49309913</guid></item></channel></rss>