<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: nomilk</title><link>https://news.ycombinator.com/user?id=nomilk</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 29 May 2026 23:14:40 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=nomilk" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by nomilk in "The just-say-no engineer was a ZIRP phenomenon"]]></title><description><![CDATA[
<p>> A "just say yes" attitude leads to certain disaster<p>Disaster's a possibility. But if an idea has a 1% chance of success, "just say no" usually assures failure, whereas "just say yes" is a shot at that 1% chance.</p>
]]></description><pubDate>Wed, 27 May 2026 06:05:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=48290287</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48290287</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48290287</guid></item><item><title><![CDATA[New comment by nomilk in "The just-say-no engineer was a ZIRP phenomenon"]]></title><description><![CDATA[
<p>> think of this as the just-say-no engineer, as opposed to the just-say-yes engineer. The just-say-yes engineer is obsessed with moving fast, approves code changes by default, values MTTR over MTBF, and tends to ship a lot of code. The just-say-no engineer is obsessed with quality, is happy to move slowly, and blocks code changes by default.<p>Love the concept of the 'just-say-yes' engineer vs 'just-say-no' engineer (and corresponding prioritisation of MTTR over MTBF).<p>I'm definitely a 'just-say-yes' with the caveat that bad architectural choices can be super painful to fix later, and features become a lot harder to fix when they have users as opposed to before launch (so I'm a little bit 'just-say-no', or at least 'just-think-for-a-bit-first').<p>I also think the balance between 'just-say-yes' and 'just-say-no' really depends a lot on the project. If it's finance or healthcare, perhaps 'no' by default is best. But if it's a silly startup idea, YOLO.</p>
]]></description><pubDate>Wed, 27 May 2026 04:58:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=48289851</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48289851</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48289851</guid></item><item><title><![CDATA[New comment by nomilk in "GitHub Actions was down"]]></title><description><![CDATA[
<p>I see the benefit (it avoids the “works on my machine” problem), but my rails app isn’t too fancy and works on heroku ~100% of the time when it works on the dev machine. Making an intermediate build redundant (technically not entirely but it’s just not worth the effort).<p>For small teams it could be as simple as everyone agreeing to ensure tests pass on main before pushing to prod.</p>
]]></description><pubDate>Tue, 26 May 2026 19:37:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=48284894</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48284894</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48284894</guid></item><item><title><![CDATA[New comment by nomilk in "The Highest Break in Professional Snooker – Ronnie O'Sullivan – 153 [video]"]]></title><description><![CDATA[
<p>For any non-snooker players: the theoretical maximum break you can usually get is 147, by sinking all 15 red balls each followed by a black (the highest scoring coloured ball) for 15 x 1 + 15 x 7 = 120. Then sinking each of the coloured balls for 2 + 3 + 4 + 5 + 6 + 7 = 27. This makes the maximum break 147.<p>But Ronnie's opponent fouled at the start, which meant Ronnie was given the ability to nominate any coloured ball as though it were a red ball. He nominated the green as the free ball and sunk it as if it were a red (scoring 1 point), then potted the black (7 points). So he had an extra 8 points right at the start.<p>Then he managed to sink a red (1 point) followed by the black (7 points) a total of 13 times, and a red followed by the pink (6 points) twice.<p>8 + 145 = 153 (highest ever).</p>
]]></description><pubDate>Tue, 26 May 2026 18:26:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=48283745</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48283745</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48283745</guid></item><item><title><![CDATA[The Highest Break in Professional Snooker – Ronnie O'Sullivan – 153 [video]]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.youtube.com/watch?v=vM3QucWQygg">https://www.youtube.com/watch?v=vM3QucWQygg</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48283568">https://news.ycombinator.com/item?id=48283568</a></p>
<p>Points: 2</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 26 May 2026 18:15:46 +0000</pubDate><link>https://www.youtube.com/watch?v=vM3QucWQygg</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48283568</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48283568</guid></item><item><title><![CDATA[New comment by nomilk in "GitHub Actions was down"]]></title><description><![CDATA[
<p>I think it comes down to risk tolerance. For an established company that wants to avoid upsetting users at all costs, CI/CD makes sense. But for a nimble 'move fast and break things' startup, it can steal dev time for very little upside.<p>Say a disaster happens and someone pushes to main without running tests, 9 times out of 10 it will be of ~zero consequence (either the code works first time, it was a cosmetic change that hardly affected users etc).<p>I know there are horror stories and CI/CD would have prevented some of those, but IME they're just not that common nor severe for small operations, and even when they happen, only a small subset are irreversible/unfixable.</p>
]]></description><pubDate>Tue, 26 May 2026 17:56:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48283257</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48283257</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48283257</guid></item><item><title><![CDATA[New comment by nomilk in "Incident with Actions and Pages"]]></title><description><![CDATA[
<p>> How do you ensure you didn’t forget to run the tests?<p>Reasonable concern. In ~10 years of indy development, I haven't forgotten to run tests before pushing to main, ever. So setting up and maintaining complicated machinery to solve a problem that could (but never has) happened doesn't justify taking focus off other more important things, namely building.<p>The benefit probably increases with team size (I'm a team of 1, so I appreciate the luxury of being able to dodge CI/CD entirely).</p>
]]></description><pubDate>Tue, 26 May 2026 16:59:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=48282455</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48282455</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48282455</guid></item><item><title><![CDATA[New comment by nomilk in "GitHub Actions was down"]]></title><description><![CDATA[
<p>Running tests locally. It's primitive, but incredibly reliable, and a breeze to debug if (big if) there is any dependency issue.</p>
]]></description><pubDate>Tue, 26 May 2026 16:12:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48281721</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48281721</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48281721</guid></item><item><title><![CDATA[New comment by nomilk in "Incident with Actions and Pages"]]></title><description><![CDATA[
<p>As an Indy hacker I want to see GitHub succeed, but I ditched actions years ago - (shocking) false economy. Spend entire nights pushing to actions over and over only for complaints about weird/niche dependency issues and other oddities - the cycle time's just too slow and the DX is no fun (my pain doesn't even factor in outages; just the feature itself as it's intended to be experienced). I want to spend time talking to users and building features, not debugging weird syntax or dependency issues on a remote machine non-interactively.<p>So why are Actions so unreliable anyway? Occam's Razor would probably suggest the domain is inherently complex/difficult; but other providers show that reliability is possible. What would Occam's Razor suggest next? Poor management..?</p>
]]></description><pubDate>Tue, 26 May 2026 16:06:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48281632</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48281632</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48281632</guid></item><item><title><![CDATA[New comment by nomilk in "SpaceX not the behemoth everyone thought"]]></title><description><![CDATA[
<p>tl;dr<p>> It's expected to be the largest IPO ever...but the prospectus shows just how much the IPO depends on expectations for future growth<p>Same goes for every IPO. One point of difference about SpaceX is those involved do have a track record for delivery.</p>
]]></description><pubDate>Fri, 22 May 2026 05:00:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=48232156</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48232156</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48232156</guid></item><item><title><![CDATA[New comment by nomilk in "Spotify will start reserving concert tickets for fans"]]></title><description><![CDATA[
<p>So long as something can be bought for x and sold for y (where y>x) there'll be an economic incentive to do so.<p>So instead of scalpers trying to simply get to the front of the queue, they'll be automating plays on spotify (hogging bandwidth, something spotify is already stingy with), and 'sharing' tracks with others, meaning it incentivises spam and fake activity.<p>Probably not a big issue to be fair, and if it only works legitimately 10% of the time it's still a win.<p>But if there's one company that can take a decent idea and execute poorly, it's Spotify.</p>
]]></description><pubDate>Fri, 22 May 2026 04:37:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=48231999</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48231999</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48231999</guid></item><item><title><![CDATA[Rule of Thirds]]></title><description><![CDATA[
<p>Article URL: <a href="https://en.wikipedia.org/wiki/Rule_of_thirds">https://en.wikipedia.org/wiki/Rule_of_thirds</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48218000">https://news.ycombinator.com/item?id=48218000</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 21 May 2026 04:51:33 +0000</pubDate><link>https://en.wikipedia.org/wiki/Rule_of_thirds</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48218000</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48218000</guid></item><item><title><![CDATA[New comment by nomilk in "Gemini 3.5 Flash"]]></title><description><![CDATA[
<p>'Pelicans' should be the unit of measurement for model prices, rather than tokens.</p>
]]></description><pubDate>Wed, 20 May 2026 09:43:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=48205262</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48205262</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48205262</guid></item><item><title><![CDATA[New comment by nomilk in "FiveThirtyEight articles on the Internet Archive"]]></title><description><![CDATA[
<p>Curious why they're broken, as the wayback machine seems to be able to run javascript. Do the visualisations rely on a server (or some other assets not included in wayback machine's crawl)?</p>
]]></description><pubDate>Wed, 20 May 2026 09:34:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=48205196</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48205196</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48205196</guid></item><item><title><![CDATA[New comment by nomilk in "India's hottest district shuts at 10 am as mercury breaches 48 C mark"]]></title><description><![CDATA[
<p>Wonder how much the removal of trees and bitumening/concreting of surface areas contributes to radiative heating from the sun which then increases the temp of surrounding air, especially on still days.</p>
]]></description><pubDate>Wed, 20 May 2026 06:18:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=48203772</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48203772</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48203772</guid></item><item><title><![CDATA[New comment by nomilk in "GitHub is investigating unauthorized access to their internal repositories"]]></title><description><![CDATA[
<p>Pre-AI, having access to code (e.g. if it leaked or even just open source) could allow hackers to more easily discover exploits. I wonder if that threat is now much more severe in the age of AI. Thankfully GitHub have probably themselves run their code through many AI security tools so any vulnerabilities would have already been found and patched. Hopefully.</p>
]]></description><pubDate>Wed, 20 May 2026 06:14:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=48203741</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48203741</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48203741</guid></item><item><title><![CDATA[New comment by nomilk in "FiveThirtyEight articles on the Internet Archive"]]></title><description><![CDATA[
<p>Couldn't figure out why archiving FTE aricles matters, but a quick search yields:<p>> Thousands of FiveThirtyEight articles seemingly vanish from the internet<p><a href="https://www.editorandpublisher.com/stories/thousands-of-fivethirtyeight-articles-seemingly-vanish-from-the-internet,261686" rel="nofollow">https://www.editorandpublisher.com/stories/thousands-of-five...</a><p>And discussions here on hn:<p>ABC News has taken all FiveThirtyEight articles offline <a href="https://news.ycombinator.com/item?id=48152553">https://news.ycombinator.com/item?id=48152553</a><p>Disney erased FiveThirtyEight (article by Nate himself) <a href="https://news.ycombinator.com/item?id=48197703">https://news.ycombinator.com/item?id=48197703</a></p>
]]></description><pubDate>Wed, 20 May 2026 03:08:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=48202647</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48202647</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48202647</guid></item><item><title><![CDATA[New comment by nomilk in "Cannibalistic attacks between gray seals leave telltale “corkscrew” injuries"]]></title><description><![CDATA[
<p>> The males may be seeking added nutrients in high-calorie blubber to boost their mating value during the breeding season, a time when bulls usually fast, Langley speculates.<p>Wonder if the male killer is of the same bloodline? Lions often opportunistically kill offspring of other males to reduce competition for their own offspring and to bring females into estrous.<p>EDIT: FWIW I asked claude and it says<p>> Gray seals have a promiscuous, harem-based mating system, but paternity is diffuse and males don't guard specific females long-term the way lions do. A bull has little way of "knowing" which pups are his rivals' offspring vs. his own.<p>So seems unlikely (according to claude).</p>
]]></description><pubDate>Mon, 18 May 2026 06:56:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=48176321</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48176321</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48176321</guid></item><item><title><![CDATA[Should you move to Silicon Valley? [video]]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.youtube.com/watch?v=QHJkUw31YX8">https://www.youtube.com/watch?v=QHJkUw31YX8</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48166352">https://news.ycombinator.com/item?id=48166352</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Sun, 17 May 2026 05:49:52 +0000</pubDate><link>https://www.youtube.com/watch?v=QHJkUw31YX8</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48166352</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48166352</guid></item><item><title><![CDATA[Ask HN: Are SaaS businesses going to zero?]]></title><description><![CDATA[
<p>For at least 15 years, MindBody (booking app for yoga/pilates studios) cost ~$400 AUD/month for basic functionality (there existed cheaper plans but those missed critical features).<p>Today, it goes for $89/month - a 78% price reduction in just a couple of years<p>I can only guess this is due to market saturation due to it being relatively low-hanging fruit for startups to nibble at.<p>Such a dramatic fall in price makes me wonder if the end-game is a price war which sees all SaaS prices fall, potentially to $0 for those with low/no switching cost</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48130604">https://news.ycombinator.com/item?id=48130604</a></p>
<p>Points: 2</p>
<p># Comments: 11</p>
]]></description><pubDate>Thu, 14 May 2026 03:01:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=48130604</link><dc:creator>nomilk</dc:creator><comments>https://news.ycombinator.com/item?id=48130604</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48130604</guid></item></channel></rss>