<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: isotropy</title><link>https://news.ycombinator.com/user?id=isotropy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 19 Oct 2026 10:45:56 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=isotropy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by isotropy in "The Duodecimal Bulletin, Vol. 55, No. 1, Year 1209 [pdf]"]]></title><description><![CDATA[
<p>So…if we had already been using a base-12 counting system when metric came along, we would have the best of both worlds.</p>
]]></description><pubDate>Tue, 23 Dec 2025 15:38:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=46366161</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=46366161</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46366161</guid></item><item><title><![CDATA[New comment by isotropy in "Microservices should form a polytree"]]></title><description><![CDATA[
<p>Without necessarily endorsing the article's ideas....I took this to be like the diamond-inheritance problem.<p>If service A feeds both B and C, and they both feed service D, then D can receive an incoherent view of what A did, because nothing forces B and C to keep their stories straight.  But B and C can still both be following their own spec perfectly, so there's no bug in any single service.  Now it's not clear whose job it is to fix things.</p>
]]></description><pubDate>Fri, 12 Dec 2025 18:09:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=46246828</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=46246828</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46246828</guid></item><item><title><![CDATA[New comment by isotropy in "996"]]></title><description><![CDATA[
<p>Offer non-diluting liquidation preferences for 996 and we can talk.</p>
]]></description><pubDate>Sat, 06 Sep 2025 17:24:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=45151162</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=45151162</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45151162</guid></item><item><title><![CDATA[New comment by isotropy in "The Big OOPs: Anatomy of a Thirty-Five Year Mistake"]]></title><description><![CDATA[
<p>OOPs = "object-oriented programming", BUT it's a more restrained and thoughtful complaint than just "objects suck" or "inheritance sucks".  He cabins it pretty clearly at 11:00 minutes in:  "compile-time hierarchy of encapsulation that matches the domain model was a mistake"</p>
]]></description><pubDate>Sat, 19 Jul 2025 17:17:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=44617356</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=44617356</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44617356</guid></item><item><title><![CDATA[New comment by isotropy in "The Internet's Time Is Flawed–Why No One Is Talking About It"]]></title><description><![CDATA[
<p>Ouch:  fair enough.</p>
]]></description><pubDate>Sat, 15 Feb 2025 04:45:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=43055956</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=43055956</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43055956</guid></item><item><title><![CDATA[New comment by isotropy in "The Internet's Time Is Flawed–Why No One Is Talking About It"]]></title><description><![CDATA[
<p>CERN, for managing highly-synchronized beam pulses applied km apart from each other:  <a href="https://white-rabbit.web.cern.ch/" rel="nofollow">https://white-rabbit.web.cern.ch/</a></p>
]]></description><pubDate>Sat, 15 Feb 2025 01:07:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=43054815</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=43054815</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43054815</guid></item><item><title><![CDATA[New comment by isotropy in "Show HN: Play with real quantum physics in your browser"]]></title><description><![CDATA[
<p>Empirically, human-flipped coins have about a 1% bias toward the same side they started on:  <a href="https://www.ams.org/publicoutreach/math-history/hap7-fifty-one-percent.pdf" rel="nofollow">https://www.ams.org/publicoutreach/math-history/hap7-fifty-o...</a></p>
]]></description><pubDate>Fri, 07 Feb 2025 14:46:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=42973159</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=42973159</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42973159</guid></item><item><title><![CDATA[New comment by isotropy in "Database mocks are just not worth it"]]></title><description><![CDATA[
<p>I've seen a db mock work when 1) there was a small subteam in charge of the OR-mapping, schema structure, and included a DBA; and 2) also a design policy from the architect that all objects had to come out of factories.  Under those specific circumstances, having the mock - used solely as a per-developer object cache imitating the factory interface - was critical for unblocking the people working on business logic and front-end.<p>I wouldn't structure a team that way now.</p>
]]></description><pubDate>Mon, 30 Dec 2024 21:06:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=42553524</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=42553524</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42553524</guid></item><item><title><![CDATA[New comment by isotropy in "Numbers Are Leaves"]]></title><description><![CDATA[
<p>I like this - nice playing around.  We usually think of this kind of tree as having directed edges from parent to child, e.g. from set to element. In your graphs, you're erasing the direction of the edges, which uncovers a neat little symmetry that I never thought about before.<p>All the (non-limit) von Neumann ordinals are of the form X+1 = {X, {X}}, where X is the previous ordinal in the set.  If you just look at trees of this form:<p>X+1: X <- node -> {X}, or X <- node -> node -> X<p>then you ignore the direction of the parent-child relation, you get this:<p>X+1:  X -- node -- node -- X<p>So that's why your trees are symmetric <i>as undirected graphs</i>; and of course, every lower ordinal has its own version of this symmetry, which is also contained in the tree.  All the large gaps between sections correspond to node--node edges of the larger ordinals.  Kinda neat!</p>
]]></description><pubDate>Sun, 29 Dec 2024 05:42:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=42537856</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=42537856</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42537856</guid></item><item><title><![CDATA[New comment by isotropy in "Engineers do not get to make startup mistakes when they build ledgers"]]></title><description><![CDATA[
<p>They are different:  in the U.S. that's why "freedom of the press" is also written down in the First Amendment, and historically, that's exactly how the U.S. courts have interpreted the phrase "freedom of the press" - as a (pretty) general right for anyone to use any media technology they can access to spread any ideas they want.  There are always some limits, but from the start "the press" meant "the printing press", not "institutionalized news organizations".  It's a general technology-usage right, not a specialized right for a certain group.  Everyone is allowed to do more than just talk, or even shout.  People can have different opinions on how wise that right is, but in the US at least, you are indeed free to broadcast your nonsense to millions of people, if you have the resources.</p>
]]></description><pubDate>Sat, 30 Nov 2024 21:35:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=42284208</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=42284208</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42284208</guid></item><item><title><![CDATA[New comment by isotropy in "Reasonable Person Principle"]]></title><description><![CDATA[
<p>Alice is taking a small unfair advantage of every member of the community at once.  A community and its practices is a form of commons shared by the members, so it's vulnerable to the tragedy of the commons.  If one member acts in a way that deliberately goes against the trust, that's inherently unfair to the rest of the members because it tends to push everything toward a breaking point.  If her goal depends on the community's existence or function (which if it doesn't, why is she even around?), then whatever her goal, Alice has gone after it in a way that takes unfair advantage of everyone else's commitment to the system.  Even if Alice's action doesn't cause a final breakdown, she's moved things in the wrong direction for her own purposes.</p>
]]></description><pubDate>Mon, 04 Nov 2024 05:35:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=42038807</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=42038807</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42038807</guid></item><item><title><![CDATA[New comment by isotropy in ""Comedy is search" – theory on how jokes work"]]></title><description><![CDATA[
<p>Tone-of-voice example (not mine):  "It. Just. Works."  vs  "It juuuuust works."</p>
]]></description><pubDate>Tue, 01 Oct 2024 12:54:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=41707713</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=41707713</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41707713</guid></item><item><title><![CDATA[New comment by isotropy in "Starting Hospice"]]></title><description><![CDATA[
<p>Thank you for sharing so much of yourself with us these past months.</p>
]]></description><pubDate>Mon, 05 Aug 2024 04:28:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=41158189</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=41158189</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41158189</guid></item><item><title><![CDATA[New comment by isotropy in "A bunch of programming advice I'd give to myself 15 years ago"]]></title><description><![CDATA[
<p>> I'm not sure "it can be generalized to an undecidable problem" really explains why it's hard....<p>Hah!  I agree with this.  :)</p>
]]></description><pubDate>Wed, 03 Jul 2024 19:51:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=40869423</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40869423</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40869423</guid></item><item><title><![CDATA[New comment by isotropy in "Dear Julia, Dear Yuri: A mathematical correspondence (2022)"]]></title><description><![CDATA[
<p>In fact, according to the Esolang Wiki [<a href="https://esolangs.org/wiki/List_of_ideas#Mathematics" rel="nofollow">https://esolangs.org/wiki/List_of_ideas#Mathematics</a>] , Gregory Chaitin apparently has built a Diophantine equation whose parameters encode an entire Lisp interpreter.</p>
]]></description><pubDate>Wed, 03 Jul 2024 19:37:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=40869300</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40869300</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40869300</guid></item><item><title><![CDATA[New comment by isotropy in "Dear Julia, Dear Yuri: A mathematical correspondence (2022)"]]></title><description><![CDATA[
<p>Yeah, this is a little bit subtle.  Please ignore the lack of rigor below, but this is my understanding:  They aren't looking at a particular polynomial like 4x + 3y = 2.  That has a solution x=2, y=-2, but they don't really care about the exact value for (x, y), just that it's integers.  They're more interested in the parameters: (4, 3, 2), and in general Ax + By = C.  If you like, it's almost like hyper parameter tuning:  what are the parameter settings for (A, B, C) where I can get this shape of equation to "work", e.g. give me acceptable x and y?  A "Diophantine set" is a family of parameters that all work.  It turns out you can think of "parameters of a given shape of Diophantine equation" as an exotic programming paradigm.<p>Fermat:  x^N + y^N = z^N.  The Diophantine set only has the number N=2, because Fermat's Last Theorem tells us that no other possible N will work if x, y, z have to be integers.  This is just a finite set.<p>Other polynomial expressions work with an infinite number of parameter settings:  Pell's equation is x^2 - N*y^2 = 1.  In this case, every N that is not a square will work.  This is an infinite set.<p>Because a lot of the parameter sets are infinite like this, the size of the parameter set are instead measured using big-O notation.  For Fermat's Last Theorem, {N=2} is constant, so big-O(1).  For Pell's equation, {N not a square} is O(N).  For other Diophantine expressions, the parameter settings are O(N^2), or O(2^N), or any other growth function you want that's achievable with Turing machines.<p>And this is the essence of what MRDP proved.  Robinson, Davis, Putnam, and Matiyasevich over several papers proved that if you could encode a set that grew roughly like O(2^N), you also could encode any other computable set in the parameters.  Approximately, demonstrating an exponentially-fast-growing family of parameters for some specific Diophantine problem was enough for Diophantine problems as a whole to be Turing complete.  Matiyasevich's clinching discovery was a concrete example using the Fibonacci numbers.</p>
]]></description><pubDate>Wed, 03 Jul 2024 19:29:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=40869247</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40869247</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40869247</guid></item><item><title><![CDATA[New comment by isotropy in "A bunch of programming advice I'd give to myself 15 years ago"]]></title><description><![CDATA[
<p>Fusion:  Turbulence, plus Naiver-Stokes was known to be hard, plus adding in EM fields, plus the exothermic state change of the nuclei fusing introduces discontinuous jumps in the free energy.<p>Collatz:  if you replace 1 and 3 with arbitrary parameters, Conway showed that this class of problems is undecidable, so any particular instance could be arbitrarily hard.</p>
]]></description><pubDate>Sun, 30 Jun 2024 15:11:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=40837616</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40837616</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40837616</guid></item><item><title><![CDATA[New comment by isotropy in "I Add 3-25 Seconds of Latency to Every Page I Visit (2020)"]]></title><description><![CDATA[
<p>Not OP but for me, it’s that public answers here are available to all of us.  That’s great!</p>
]]></description><pubDate>Wed, 26 Jun 2024 18:23:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=40802882</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40802882</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40802882</guid></item><item><title><![CDATA[New comment by isotropy in "The Weird Nerd comes with trade-offs"]]></title><description><![CDATA[
<p>I read this as basically arguing that our filters throw up too many false negatives, like Kariko, in a high-risk/high-reward environment.  It’s saying the cost of false negatives is way higher than the system realizes, and that’s because the system has drifted to be too much like the collaborative, incremental workplace that most of us live in.  Typical work teams pay a high cost for false positives when hiring, so they guard against them at the cost of way more false negatives.  The doesn’t work as well for moonshot fields.</p>
]]></description><pubDate>Sun, 09 Jun 2024 17:41:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=40626090</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40626090</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40626090</guid></item><item><title><![CDATA[New comment by isotropy in "Disappointment"]]></title><description><![CDATA[
<p>Danny Calegari's essay "Disappointment" in the Notices (<a href="https://www.ams.org/journals/notices/202309/noti2782/noti2782.html" rel="nofollow">https://www.ams.org/journals/notices/202309/noti2782/noti278...</a>) is a nice reflection on how to think  - and try to feel - about failures.</p>
]]></description><pubDate>Thu, 23 May 2024 14:36:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=40455266</link><dc:creator>isotropy</dc:creator><comments>https://news.ycombinator.com/item?id=40455266</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40455266</guid></item></channel></rss>