<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">too many good things to respond to, and I keep putting off saying anything until I get my head into order, which of course I never will<div><br></div><div>also too many good things to read, especially when I am stuck and looking for a time-waste</div><div><br></div><div>so in no particular order</div><div><br></div><div>Marcus had a couple of posts that shook me out of my normal unimaginative mindset and reminded me of ways I should see this, from arguments I have already been making for a long time but put out of mind:</div><div><br></div><div>\u2014 there was the reply that got to me on Aug 2nd, which began with \u201cI<span style="font-family: Calibri, sans-serif; font-size: 14.666667px;"> </span><span style="font-family: Calibri, sans-serif; font-size: 14.666667px;">use both Claude Code and Codex heavily,</span><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"> \u2026.\u201d in reply to my original post about junk papers being written by people who are effectively imprisoned workers in academic junior positions, quite close to the call-center prisoners in SE Asia, and Marcus\u2019s argument that the solution to problems with LLMs is more LLMs: that paper writing and reading is all, going forward, to be machine-first and human-(when?)\u2026 But crucially with examples of how, for code architecture, the better tools are doing a very good job of seeking and achieving \u201cgrounding on factual things\u201d. And then another post on Aug 4th in reply to Glen\u2019s endorsement of micromanaging, to which Marcus\u2019s answer (as I read it) was: diminishing returns (or already diminished).</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">the thing I wanted to send back in reply to these posts is the argument for opportunity in all this (so, signing off on Marcus\u2019s objection). I have been trying to sell people on the argument, for many years now, that \u201ccomplex systems\u201d or \u201ccomplexity science\u201d isn\u2019t characterized by any particular domain or phenomena of inquiry (nobody would argue against that), and just as much, that it isn\u2019t characterized to an important degree by any specific attributes or aspects: being non-decomposable, or adaptive, or evolutionary, or whatever (I have many people in mind who would disagree with me here, and say those are the definitive things). What I argued it was, rather, was whatever is over-the-fence from the most that can fit into human heads. Used to be that we advanced knowledge by cramming as much of what existed as possible into a mind, and hoping the mind would see an invention. But von Neumann was about the last of that species that was really a type-specimen. Most of the low-hanging fruit from that way of doing things has been eaten. Now we need to be responsible for best-level understanding of more learned-areas that bear on a problem than any person can learn. But ideas still happen, it seems, within individuals. So what do we do? What kind of community can use \u2014 properly \u2014 more than any of its members can understand? That was, by my argument, the \u201cnew\u201d problem to which \u201ccomplex systems\u201d was supposed to contribute some new insight or practice.</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">But in my post that prompted Marcus\u2019s original objection, I was still (by metaphor) only willing to sign off on the use of LLMs as appliances. The Lee Sedol or Terry Tao approach, where we know what the problem is (playing more advanced Go, creating new math), and the LLMs expose regions of practice that the people-community had never opened, because people herd and miss things. There, I was being dumbly too narrow. If the new Big Data is a net over the world, capable of filtering and rendering, it can in some way \u201ccover\u201d everything that is available to be covered. Marcus\u2019s code-creation cases show that it can do quite a good job of abstracting precepts of architecture. So the right question for complex systems people is: how much of a model is the already-demonstrated performance, for whatever counts as \u201cunderstanding\u201d? Up to now that has been one of these cultural hand-me-down words that we can use with each other, and we don\u2019t need to be able to articulate \u201cwhat it (understanding) means\u201d, since by exchanging it was can put each other in the intended frames of mind. But to make good use of it with this non-people-thing, maybe we should do a better job of articulating what \u201cunderstanding\u201d something means, as it bears on how we want to create. Or more generally, what kind of life going forward we would find tolerable?</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">It\u2019s also cicada season, and I am aware, while they sing themselves to depletion and fairly early death all over the streets and parks and buildings, that it is useful to try to deal with the question Why do cicadas do anything? The problem-word being \u201cwhy\u201d. If we can get that right for cicadas, we probably have most of what we need for people. Trying to do it for cicadas is helpful because it deprives us of the crutch of attaching too much significance to the speaker\u2019s own personhood (my rendering of another of Marcus\u2019s expressions).</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">Then there was Jon\u2019s reply on Aug 3rd to my poke at Bourbak (which I sort of expected and hoped for). Apart from many fond memories of RLM, a building that I was told the physics department had designed, and that the lowest of the Soviet era would have been proud of: energetically rejected any kind of elegance or grace and managed still not to achieve functionality; elevators that cluster on all floors, while the Otis employee stands in the lobby and watches them and declares \u201cour elevators do not cluster\u201d, or the escalators on the bottom 3 floors that, when the building opened, had been coordinated raster-wise like those in department stores, but the kid-traffic got so high that the people-flow jammed like gravel in a hopper, and kids were jumping off the sides to the floors below in the Kaaba-crush, or the main lecture hall where big concrete posts obscure the view of the speaker and slides for about 15% of the audience \u2014 </span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">Apart from all that, there were two actual things to say. Diaconis wasn\u2019t objecting to the insights and content of the mathematicians of the Bourbak school and its descendents. As Jon says, a ton of that was creative and consequential. Diaconis was objecting to the aesthetic that mangled (in his view) the effort to communicate, losing faithfulness even to how the creators thought, and putting a needless obstacle in front of others to understand them. Since Diaconis\u2019s lectures have been, for me, so uncommonly beautiful and self-propelling to follow, I took him (as he wanted to be taken) as an example that it didn\u2019t always have to be a slog, in everything.</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">But the other point upon reading Jon was that, in a way, the current Techlords\u2019 aspiration to upload themselves into an engineered thing isn\u2019t new at all. It\u2019s what mathematicians have always wanted to do, and that David Hilbert articulated most coherently: Can you create a formalism that will carry _all_ of what you mean, so that _nothing_ is left that depends on you and that has not been exported to the formalism. Can the formalism on its own have metaphysical substance? Of course, I have no ability to appreciate the Hilbert program the way a mathematician can, so I am out of my lane, and I know it (Glen\u2019s ultracrepidarian). But suddenly it seems that everything new is old again, and this theme has been there for a long time.</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">And then finally today, getting only part-way through Celine Nguyen\u2019s piece on taste that Glen sent (before needing to stop fooling around and work), I was reminded of Darwin and Mendel. Darwin hadn\u2019t thought through the fact that the heredity model as he understood it would be mixing paint and would bleach out the preservation of variation. It was the Modern Synthesis that brought in Mendel, and said No; it\u2019s like shuffling un-mixable cards so variation can be preserved. But there is this lovely paper</span></font></div><div><div style="display: block;"><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://www.pnas.org/doi/10.1073/pnas.0603780103"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:228px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://www.pnas.org/doi/10.1073/pnas.0603780103" dir="ltr" role="button" draggable="false" width="228"><table style="table-layout:fixed;border-collapse:collapse;width:228px;background-color:#8C7D72;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="228"><tbody><tr><td vertical-align="center" align="center"><img style="width:228px;filter:brightness(0.97);height:307px;" width="228" height="307" draggable="false" class="lp-rich-link-mediaImage" alt="pnas.2006.103.issue-28.cover.gif" src="cid:69A0BBAD-BBCF-486A-A9EE-AAC5324A1D79"></td></tr><tr><td vertical-align="center"><table bgcolor="#8C7D72" cellpadding="0" cellspacing="0" width="228" style="table-layout:fixed;font-family:-apple-system, Helvetica, Arial, sans-serif;background-color:rgba(140, 125, 114, 1);-apple-color-filter:initial;" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://www.pnas.org/doi/10.1073/pnas.0603780103" style="text-decoration: none" draggable="false"><font color="#FFFFFF" style="color: rgba(255, 255, 255, 0.847059);">Collective evolution and the genetic code</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://www.pnas.org/doi/10.1073/pnas.0603780103" style="text-decoration: none" draggable="false"><font color="#FFFFFF" style="color: rgba(255, 255, 255, 0.54902);">pnas.org</font></a></div></div></td></tr></tbody></table></td></tr></tbody></table></a></div></div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"></span></font></div><div><span style="font-family: Calibri, sans-serif; font-size: 14.666667px;">(seems not to be paywalled)</span></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">that says, even with genes, if there is no bundling into genomes, you go into a \u201cthermodynamic\u201d regime, where there are few attractors but they are very fast and robust, whereas if you block lateral transfer, you go into the \u201cDarwinian\u201d regime where variation is preserved because mixing is inhibited: </span></font></div><div><br></div><div>I never liked the reference to integrated big-data/AI/LLM-etc systems as \u201cconscious\u201d or whatever, because the word is bad enough that the main content I can see in it is human projection, and relatively little of understanding, since we didn\u2019t understand it in the first place. But it does seem right to say it is a net over the world, and that that will be a new thing for us to deal with, unlike anything at this scale and in this area that we have ever lived with before. The economy, and fossil-fuel-powered global transport, were two much narrower nets over the world, and already we see how they have changed life, and when they get into snags after we have committed all our dependence to them and re-orgznized society and infrastructure and demography and population around them, we have not been good at getting ourselves untangled. </div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size: 14.666667px;">So the argument that people preserved variety because they were incapable of learning enough to blend it all out (returning to Nguyen), and that now that barrier is removed and we stand to lose a lot, becomes the distillation of a lot of people\u2019s varied worries about commodity use of LLMs to replace everything they find laborious or tiresome (meaning, all of living). Of course Marcus can rebut that, too, saying that LLMs can be set up to prioritize maintenance of variety as easily as they can be set up to do anything else, an argument we have seen demonstrated on much older technology (which shows whatever it shows): </span></font></div><div><div></div><div><div style="display: block;"><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://picbreeder.net/7338"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://picbreeder.net/7338" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#E6E6E6;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center"><table bgcolor="#E6E6E6" cellpadding="0" cellspacing="0" width="300" style="table-layout:fixed;font-family:-apple-system, Helvetica, Arial, sans-serif;background-color:rgba(230, 230, 230, 1);-apple-color-filter:initial;" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://picbreeder.net/7338" style="text-decoration: none" draggable="false"><font color="#272727" style="color: rgba(0, 0, 0, 0.847059);">Picbreeder</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://picbreeder.net/7338" style="text-decoration: none" draggable="false"><font color="#808080" style="color: rgba(0, 0, 0, 0.498039);">picbreeder.net</font></a></div></div></td><td style="padding:6px 12px 6px 0px;" class="lp-rich-link-captionBar-rightIconItem" width="30"><a rel="nofollow" href="https://picbreeder.net/7338" draggable="false"><img style="pointer-events:none !important;display:inline-block;width:30px;height:30px;border-radius:3px;" width="30" height="30" draggable="false" class="lp-rich-link-captionBar-rightIcon" alt="icon.gif" src="cid:5F11A524-EEBF-47CB-A787-0C665B24D50F"></a></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br><br>Anyway. As I said; anyway\u2026</div><div><br></div><div>Eric</div><div><br></div><div><br><br><br><blockquote type="cite"><div>On Aug 13, 2026, at 1:12, glen <gepr@ropella.name> wrote:</div><br class="Apple-interchange-newline"><div><div>It likely matters *how* you present the posts to the machine. Did you simply point it to the archives? Both sets? Or did you download it all and curate it? A good thing to do might be to remove the footer that gets repeated a billion times in an active thread because people refuse to clean up their posts. [grrr]<br><br>The threading indices might be more interesting than the by-date indices:<br><br>https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fredfish.com%2fpipermail%2ffriam_redfish.com%2f2026-August%2fthread.html%23start&c=E,1,c9mtOl3J2x_2DdPKBRWBt624pJITZPSnp2Lejvp5fsGACtEO8OpvtM6guXyt0BeylOd7azscbOjvgrsMp9FDgoUMI9ZOsPMv7Y_WBAGDTf_I&typo=1<br><br>versus<br><br>https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fredfish.com%2fpipermail%2ffriam_redfish.com%2f2026-August%2fdate.html&c=E,1,sQtH77sWTBaqht4ez2QXH5JvWv9UikFIPqxIm5ToU6Nj3gQchweI7bhHFD9elzQvJfwVcsvJwmCbdP17_3Ld_CnwLA6Hry35dX39CXQMXT0gvG_Pfg,,&typo=1<br><br>Of course, Codex could help you reorganize the corpus for each given inference type. The best thing to do might be to gather the corpus and build a queryable database. Then for any given type of inference, the LLM queries the database.<br><br>Garbage in \u2192 garbage out ... and it's clearly garbage if the machine thinks I'm funny. cf https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fasteriskmag.com%2fissues%2f15%2fwhy-we-like-things&c=E,1,Hs5H2eHOnTwk3pn-PW0zUBn5mcf-M0hO3PLIY_QFeTMkTBnhJS9ycyTBkbh2lBmUE9V1hdoSkj6J7Y9PeQ6X6fDUR5xHJVimU79t3t5coe4-YCY,&typo=1<br><br><br>On 8/12/26 8:31 AM, jofr wrote:<br><blockquote type="cite">A simple model is based on timezones. When I post something at 9 AM CET (or CEST) Central European Time, then I usually get no response before 5 PM when it it is 8 AM in California and 9 AM in Santa Fe. The posting times reflect where a person is physically located.<br>The rest is more or less unpredictable. Posts could be correlated to even more posts. Some kind of self-reinforcing bubble. It also reminds me of the famous El-Farol Bar Problem which predicts visitors for a bar. Does this bar still exist in Santa Fe?<br>https://en.wikipedia.org/wiki/El_Farol_Bar_problem<br>In general it seems to be unpredictable. I posted for example less in recent weeks because my mail server provider from New York changed the settings and I had difficulties to access this email account I am using now.<br>-J.<br>-------- Original message --------<br>From: Marcus Daniels <marcus@snoutfarm.com><br>Date: 8/12/26 5:05 PM (GMT+01:00)<br>To: The Friday Morning Applied Complexity Coffee Group <friam@redfish.com><br>Subject: Re: [FRIAM] What is FRIAM and is it still alive<br>I was looking for a (null space) model of when and why a post occurs. Like why a person would reach for the remote and change the TV station. It may have nothing to do with the coherence or silliness of any particular programming. Like going out for a cup of coffee or a smoke.<br>*From: *Friam <friam-bounces@redfish.com> on behalf of jofr <jofr@cas-group.net><br>*Date: *Wednesday, August 12, 2026 at 7:58\u202fAM<br>*To: *The Friday Morning Applied Complexity Coffee Group <friam@redfish.com><br>*Subject: *Re: [FRIAM] What is FRIAM and is it still alive<br>You mean a "credit model" depending on correspondence length and authorship time? GitHub has a statistics page for repositories which shows who has committed the most lines in what timeframe. And some open source frameworks like Ruby on Rails list their most active contributors https://contributors.rubyonrails.org<br>ChatGPT says about you Marcus that you are the most active poster by a substantial margin. You win clearly in this category.<br>Nick and Glen are funnier according to ChatGPT though. ChatGPT is particularly fond of the Nick's post "All those who think Steve was wrong raise your hands" and Glen's post "Say it again \u2026 Say it again in a different way \u2026 Again \u2026 Again, damnit!"<br>-J.<br>-------- Original message --------<br>From: Marcus Daniels <marcus@snoutfarm.com><br>Date: 8/12/26 4:28 PM (GMT+01:00)<br>To: The Friday Morning Applied Complexity Coffee Group <friam@redfish.com><br>Subject: Re: [FRIAM] What is FRIAM and is it still alive<br>Correspondence length and apparent authorship time that follows the distribution of a compile/link cycle or system integration test suite execution duration?<br>*From: *Friam <friam-bounces@redfish.com> on behalf of jofr@cas-group.net <jofr@cas-group.net><br>*Date: *Wednesday, August 12, 2026 at 4:50\u202fAM<br>*To: *The Friday Morning Applied Complexity Coffee Group <friam@redfish.com><br>*Subject: *Re: [FRIAM] What is FRIAM and is it still alive<br>ChatGPT proposed these two laws:<br>FRIAM's First Law: We take difficult philosophical problems and worry<br>them to death until someone produces either a profound insight, a<br>completely insane hypothesis, or a phrase like "quantum woo".<br>FRIAM's Second Law: If a theory is suspiciously elegant, somebody on the<br>list will throw a shoe at it.<br>The reason I have asked ChatGPT and Gemini is I am writing a new<br>self-published book, and the first chapter is about FRIAM. Their<br>summaries are surprisingly good. I asked them to find funny anecdotes in<br>the FRIAM archives and they found a post from Nick that said "OK<br>friammers, All those who think Steve was wrong raise your hands" :-)<br>If you do NOT want to be mentioned in the chapter because it is too much<br>quantum woo for you then please let me know or raise your hand. Will<br>share a draft in a few days.<br>-J.<br></blockquote><br><br>-- <br>8647 \u22a5 \u0250\u05df\u05df\u01dddo\u0279 \u01dd u\u01dd\u05df\u0183<br>\u1f45\u03c4\u03b5 oi \u03bc\u1f72\u03bd \u1f04\u03bb\u03bb\u03bf\u03b9 \u03ba\u03cd\u03bd\u03b5\u03c2 \u03c4\u03bf\u1f7a\u03c2 \u1f10\u03c7\u03d1\u03c1\u03bf\u1f7a\u03c2 \u03b4\u03ac\u03ba\u03bd\u03bf\u03c5\u03c3\u03b9\u03bd, \u1f10\u03b3\u1f70 \u03b4\u1f72 \u03c4\u03bf\u1f7a\u03c2 \u03c6\u03af\u03bb\u03bf\u03c5\u03c2, \u1f35\u03bd\u03b1 \u03c3\u03ce\u03c3\u03c9.<br><br><br>.- .-.. .-.. / ..-. --- --- - . .-. ... / .- .-. . / .-- .-. --- -. --. / ... --- -- . / .- .-. . / ..- ... . ..-. ..- .-..<br>FRIAM Applied Complexity Group listserv<br>Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbit.ly%2fvirtualfriam&c=E,1,-AHg9AEnF1yI9Ni6veUuQ8iLv4BlNcRsDChEr9C5ej7R-JvakqEzAqlyqN3ZjR7vspGzBitQQEeO2fAx4c25BmD31CtTub0rKtRjU_qt-oT_gkmWGVAEqdXy&typo=1<br>to (un)subscribe https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fredfish.com%2fmailman%2flistinfo%2ffriam_redfish.com&c=E,1,J1kjmo0OITj21RfEaiAu2GkGlc4Pos2FIoziOtAla-A5C9MvIEgo18JYiOE_HpT0D7McBpgTrXJadyVL0V0sBPAOv-ygitJKheKWZCL3UeoCpKg3vaQBr1wF-NDK&typo=1<br>FRIAM-COMIC https://linkprotect.cudasvc.com/url?a=http%3a%2f%2ffriam-comic.blogspot.com%2f&c=E,1,MPLIXP7YZufyF0pFEzDNQkNQNpO2lT51BrCvhp_O7wcgx4iAPySj6Cs0xmy_zQy6XJKFAfHmNOi1OuwYP7NU5UsLhFOhJ5Q2oSboLPh44SBz7g,,&typo=1<br>archives: 5/2017 thru present https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fredfish.com%2fpipermail%2ffriam_redfish.com%2f&c=E,1,I9Bxe2HfwJFv94Kf74g0szY9LcAHbv-3g3rdvXxA1TS0DzcR5_5_SzQks6GzWs42pfAnmqdi5Od9PKpU7bocgd0nN1-zFxC3uggMx-gKyFQEozxC&typo=1<br> 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/<br></div></div></blockquote></div><br></div></body></html>