<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: tibbar</title><link>https://news.ycombinator.com/user?id=tibbar</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 14:05:25 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=tibbar" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by tibbar in "What if remote working, not AI, is to blame for weak junior hiring?"]]></title><description><![CDATA[
<p>Given how many studies have built-in sampling bias or other surprising assumptions, I still welcome people gut-checking it vs their experience. (Plus, the stories are interesting, right?)</p>
]]></description><pubDate>Mon, 01 Jun 2026 01:05:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48351519</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48351519</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48351519</guid></item><item><title><![CDATA[New comment by tibbar in "Building durable workflows on Postgres"]]></title><description><![CDATA[
<p>Having worked for a business that made a serious go of running everything out of stored procedures, I have to say that lack of version control was a huge problem and effectively limited all development to a single person who held all the rules in their head.</p>
]]></description><pubDate>Thu, 28 May 2026 23:23:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=48316939</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48316939</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48316939</guid></item><item><title><![CDATA[New comment by tibbar in "Building durable workflows on Postgres"]]></title><description><![CDATA[
<p>lack of version control, clunky language mechanics, performance issues, etc.</p>
]]></description><pubDate>Thu, 28 May 2026 22:08:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=48316208</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48316208</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48316208</guid></item><item><title><![CDATA[New comment by tibbar in "Building durable workflows on Postgres"]]></title><description><![CDATA[
<p>This has been tried, but thousand-line stored procedures are truly a nightmare.</p>
]]></description><pubDate>Thu, 28 May 2026 20:53:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=48315306</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48315306</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48315306</guid></item><item><title><![CDATA[New comment by tibbar in "The worst job interview I ever had"]]></title><description><![CDATA[
<p>The description of the interview seems like it was explicitly non-technical, though.</p>
]]></description><pubDate>Tue, 26 May 2026 23:05:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=48287244</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48287244</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48287244</guid></item><item><title><![CDATA[Don't make fun of renowned Dan Brown]]></title><description><![CDATA[
<p>Article URL: <a href="https://jimmyakin.com/2024/03/dont-make-fun-of-renowned-dan-brown.html">https://jimmyakin.com/2024/03/dont-make-fun-of-renowned-dan-brown.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48180067">https://news.ycombinator.com/item?id=48180067</a></p>
<p>Points: 4</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 18 May 2026 14:02:48 +0000</pubDate><link>https://jimmyakin.com/2024/03/dont-make-fun-of-renowned-dan-brown.html</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48180067</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48180067</guid></item><item><title><![CDATA[New comment by tibbar in "Stochastic Parrots: Frequently Unasked Questions"]]></title><description><![CDATA[
<p>I mean, we're pretty deep into Westworld/Blade Runner-style scifi at this point. It's actually a crazy, mind-bending question to try to grasp what is going on with chatclaudini at this point. Regardless of what labels we choose or properties we choose to affirm, we're far too deep into uncanny valley for it to be very helpful.</p>
]]></description><pubDate>Sun, 17 May 2026 03:25:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48165795</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48165795</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48165795</guid></item><item><title><![CDATA[New comment by tibbar in "YC's Biggest Scandals"]]></title><description><![CDATA[
<p>LLMs often seem to have trouble determining the severity of a bug/incident/problem in a vacuum. If you run an LLM over 1000 items in parallel and ask "is this bad," it will come up with reasons for it to be bad way more than it might if it were considering all 1000 at the same time.</p>
]]></description><pubDate>Sun, 10 May 2026 19:58:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48087295</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48087295</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48087295</guid></item><item><title><![CDATA[New comment by tibbar in "YC's Biggest Scandals"]]></title><description><![CDATA[
<p>Scrolling down, a bunch of these seem to just be "the startup shut down after getting customers", which doesn't seem particularly scandalous to me?</p>
]]></description><pubDate>Sun, 10 May 2026 19:51:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48087209</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48087209</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48087209</guid></item><item><title><![CDATA[New comment by tibbar in "Redis array: short story of a long development process"]]></title><description><![CDATA[
<p>Fair point that there might be some functional changes you can suggest, but I continue to suspect that by the time this PR hit GitHub, all the most important decisions have already been finalized.</p>
]]></description><pubDate>Mon, 04 May 2026 22:33:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=48015846</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48015846</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48015846</guid></item><item><title><![CDATA[New comment by tibbar in "Redis array: short story of a long development process"]]></title><description><![CDATA[
<p>First of all, redis is amazing, and your 4 month development process speaks to the fact that you've already designed and verified correctness super thoroughly.<p>... just speaking as someone who sometimes has to review very long PRs sometimes, though, I feel like 25% is a roughly normal level of "signal to noise." 5,000 lines of core logic is a LOT, and the tests and dependencies do still need to be read.<p>EDIT: I feel like the problem, as a reviewer, is processing 4 months of intensive research/development and providing useful feedback. At that point, there's probably not much major input you can have into the core architecture or strategy, so you're probably not providing much more than a bugbot at that point.</p>
]]></description><pubDate>Mon, 04 May 2026 18:16:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=48012637</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48012637</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48012637</guid></item><item><title><![CDATA[New comment by tibbar in "Redis array: short story of a long development process"]]></title><description><![CDATA[
<p>Oh wow, I didn't realize that Redis is still mostly just authored by antirez! (My understanding is that he had left for some time and then returned to the project.) That is, honestly, pretty amazing. Well, redis is great and clearly it's worked out.</p>
]]></description><pubDate>Mon, 04 May 2026 18:10:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48012547</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48012547</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48012547</guid></item><item><title><![CDATA[New comment by tibbar in "GitHub Is Down"]]></title><description><![CDATA[
<p>I'm curious, do people around you use AI? Because in my own workplace, people use lots of AI, and they ship lots of PRs, which correspond to actual features on the roadmap. I've been doing this a long time, and there is a whole lotta stuff shipping. I'm a manager and in the handful of hours I have I'm shipping the equivalent of what I would have as a full-time eng years ago.</p>
]]></description><pubDate>Mon, 04 May 2026 18:08:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=48012527</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48012527</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48012527</guid></item><item><title><![CDATA[New comment by tibbar in "Redis array: short story of a long development process"]]></title><description><![CDATA[
<p>Reviewing 22,000 lines of code, even from antirez, with this complex of a feature set and minimal PR description sounds like a nightmare. One starts to see why major open-source software like Postgres tends to be developed on a mailing list, with intermediate design decisions discussed by the community, separate patches for different related features, incremental review, and then a spaced release cadence.</p>
]]></description><pubDate>Mon, 04 May 2026 17:44:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=48012127</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48012127</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48012127</guid></item><item><title><![CDATA[New comment by tibbar in "DAG Workflow Engine"]]></title><description><![CDATA[
<p>I was expecting to see some verbose LLM output, but actually the code has a distinctly hand-crafted feel. Nice to see! I'm not sure if "production ready" is a safe claim 7 commits in to a project ;)</p>
]]></description><pubDate>Mon, 04 May 2026 15:38:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48010070</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=48010070</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48010070</guid></item><item><title><![CDATA[Dominant Resource Fairness: Fair Allocation of Multiple Resource Types [pdf]]]></title><description><![CDATA[
<p>Article URL: <a href="https://amplab.cs.berkeley.edu/wp-content/uploads/2011/06/Dominant-Resource-Fairness-Fair-Allocation-of-Multiple-Resource-Types.pdf">https://amplab.cs.berkeley.edu/wp-content/uploads/2011/06/Dominant-Resource-Fairness-Fair-Allocation-of-Multiple-Resource-Types.pdf</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47983316">https://news.ycombinator.com/item?id=47983316</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 02 May 2026 04:31:25 +0000</pubDate><link>https://amplab.cs.berkeley.edu/wp-content/uploads/2011/06/Dominant-Resource-Fairness-Fair-Allocation-of-Multiple-Resource-Types.pdf</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=47983316</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47983316</guid></item><item><title><![CDATA[Building reliability into uncertain event delivery (2022)]]></title><description><![CDATA[
<p>Article URL: <a href="https://zendesk.engineering/building-reliability-into-uncertain-event-delivery-a09db0750ef9">https://zendesk.engineering/building-reliability-into-uncertain-event-delivery-a09db0750ef9</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47960756">https://news.ycombinator.com/item?id=47960756</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 30 Apr 2026 11:05:14 +0000</pubDate><link>https://zendesk.engineering/building-reliability-into-uncertain-event-delivery-a09db0750ef9</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=47960756</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47960756</guid></item><item><title><![CDATA[New comment by tibbar in "Nobody Got Fired for Uber's $8M Ledger Mistake?"]]></title><description><![CDATA[
<p>$8M sounds like a lot, but (a) the cost of making a material financial mistake c an easily dwarf this, and (b) the cost of the engineers maintaining the system was likely about this expensive anyway. And infra <i>is</i> expensive when you're Uber. It all seems rather overblown to me.</p>
]]></description><pubDate>Wed, 22 Apr 2026 16:44:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=47866049</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=47866049</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47866049</guid></item><item><title><![CDATA[Stripe's Payment APIs: the first 10 years (2020)]]></title><description><![CDATA[
<p>Article URL: <a href="https://stripe.dev/blog/payment-api-design">https://stripe.dev/blog/payment-api-design</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47830575">https://news.ycombinator.com/item?id=47830575</a></p>
<p>Points: 95</p>
<p># Comments: 51</p>
]]></description><pubDate>Mon, 20 Apr 2026 05:05:43 +0000</pubDate><link>https://stripe.dev/blog/payment-api-design</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=47830575</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47830575</guid></item><item><title><![CDATA[Looking back on Stripe's payment API migration]]></title><description><![CDATA[
<p>Article URL: <a href="https://jacobbrazeal.wordpress.com/2026/04/19/review-stripes-payments-apis/">https://jacobbrazeal.wordpress.com/2026/04/19/review-stripes-payments-apis/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47828724">https://news.ycombinator.com/item?id=47828724</a></p>
<p>Points: 4</p>
<p># Comments: 1</p>
]]></description><pubDate>Sun, 19 Apr 2026 23:35:49 +0000</pubDate><link>https://jacobbrazeal.wordpress.com/2026/04/19/review-stripes-payments-apis/</link><dc:creator>tibbar</dc:creator><comments>https://news.ycombinator.com/item?id=47828724</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47828724</guid></item></channel></rss>