<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" 
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:source="https://source.scripting.com/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
  <channel>
    <title>markjgsmith - Everything Feed</title>
    <description>Unified content delivery stream for markjgsmith.com.</description>
    <link>https://markjgsmith.com</link>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Nov 2026 19:15:31 GMT</lastBuildDate>
    <atom:link href="https://markjgsmith.com/dist" rel="self" type="application/rss+xml" />
    <item>
      <link>https://markjgsmith.com/notes/2026/11/18/194445/index.html</link>
      <guid isPermaLink="false">bbe2c73f-dad5-42bd-a789-658c5da8497c</guid>
      <description><![CDATA[<p>As time tends to infinity, the probability that worldo bans everything you interact with tends to infinity. And if everything is essentially banned, everything becomes very very expensive, and that&#39;s before the theft of inflation. This is why we can&#39;t have nice things. It doesn&#39;t surprise me at all that the rich hoard their wealth and money, which means there&#39;s not enough for everyone else, it&#39;s because worldo has banned everything for them too, so it costs a million dollars just to buy a loaf of bread, safely. <a href="https://markjgsmith.com/notes/2026/11/18/194445">#</a></p>]]></description>
      <pubDate>Wed, 18 Nov 2026 12:44:45 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>As time tends to infinity, the probability that worldo bans everything you interact with tends to infinity. And if everything is essentially banned, everything becomes very very expensive, and that&#39;s before the theft of inflation. This is why we can&#39;t have nice things. It doesn&#39;t surprise me at all that the rich hoard their wealth and money, which means there&#39;s not enough for everyone else, it&#39;s because worldo has banned everything for them too, so it costs a million dollars just to buy a loaf of bread, safely. <a href="https://markjgsmith.com/notes/2026/11/18/194445">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[As time tends to infinity, the probability that worldo bans everything you interact with tends to infinity. And if everything is essentially banned, everything becomes very very expensive, and that's before the theft of inflation. This is why we can't have nice things. It doesn't surprise me at all that the rich hoard their wealth and money, which means there's not enough for everyone else, it's because worldo has banned everything for them too, so it costs a million dollars just to buy a loaf of bread, safely. [#](https://markjgsmith.com/notes/2026/11/18/194445)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/18/182901/index.html</link>
      <guid isPermaLink="false">46ef9fe4-56d6-4920-a54b-6e9b8b3c3d6c</guid>
      <description><![CDATA[<p>Worldo appears to be going on a banning rampage. Today door knobs have been banned. <a href="https://markjgsmith.com/notes/2026/11/18/182901">#</a></p>]]></description>
      <pubDate>Wed, 18 Nov 2026 11:29:01 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Worldo appears to be going on a banning rampage. Today door knobs have been banned. <a href="https://markjgsmith.com/notes/2026/11/18/182901">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Worldo appears to be going on a banning rampage. Today door knobs have been banned. [#](https://markjgsmith.com/notes/2026/11/18/182901)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/18/181839/index.html</link>
      <guid isPermaLink="false">ec43f84c-21c3-46e5-adda-0c23d422046e</guid>
      <description><![CDATA[<p>The past few days I have mostly been juggling composition roots, and of course fixing unit tests. <a href="https://markjgsmith.com/notes/2026/11/18/181839">#</a></p>]]></description>
      <pubDate>Wed, 18 Nov 2026 11:18:39 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>The past few days I have mostly been juggling composition roots, and of course fixing unit tests. <a href="https://markjgsmith.com/notes/2026/11/18/181839">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[The past few days I have mostly been juggling composition roots, and of course fixing unit tests. [#](https://markjgsmith.com/notes/2026/11/18/181839)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/18/151731/index.html</link>
      <guid isPermaLink="false">3534947c-e305-489d-b87a-337b7b6bcb3a</guid>
      <description><![CDATA[<p>So tired of circles. So tired. <a href="https://markjgsmith.com/notes/2026/11/18/151731">#</a></p>]]></description>
      <pubDate>Wed, 18 Nov 2026 08:17:31 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>So tired of circles. So tired. <a href="https://markjgsmith.com/notes/2026/11/18/151731">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[So tired of circles. So tired. [#](https://markjgsmith.com/notes/2026/11/18/151731)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/18/121055/index.html</link>
      <guid isPermaLink="false">1b406b04-1a56-4a55-bb63-6784be533289</guid>
      <description><![CDATA[<p>Epidemic levels of people creating the problems that are complaining about where I am today. Eventually it just turns into a giant tangled angry mess. Sometimes it&#39;s best just to move on. If it&#39;s that important it will re-surface again sometime later. 9 times out of 10 it&#39;s not that important. <a href="https://markjgsmith.com/notes/2026/11/18/121055">#</a></p>]]></description>
      <pubDate>Wed, 18 Nov 2026 05:10:55 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Epidemic levels of people creating the problems that are complaining about where I am today. Eventually it just turns into a giant tangled angry mess. Sometimes it&#39;s best just to move on. If it&#39;s that important it will re-surface again sometime later. 9 times out of 10 it&#39;s not that important. <a href="https://markjgsmith.com/notes/2026/11/18/121055">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Epidemic levels of people creating the problems that are complaining about where I am today. Eventually it just turns into a giant tangled angry mess. Sometimes it's best just to move on. If it's that important it will re-surface again sometime later. 9 times out of 10 it's not that important. [#](https://markjgsmith.com/notes/2026/11/18/121055)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/17/135546-theguardian.com/index.html</link>
      <guid isPermaLink="false">e2d6f1e3-c038-40f0-ab85-c501033d84e1</guid>
      <description><![CDATA[<p>Germany, Austria, the Netherlands, Denmark and Greece to start deporting illegal immigrants to Rwanda in Africa. <a href="https://www.theguardian.com/world/2026/nov/16/eu-states-immigration-return-hubs-rwanda">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/17/135546-theguardian.com">#</a></p>]]></description>
      <pubDate>Tue, 17 Nov 2026 06:55:46 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Germany, Austria, the Netherlands, Denmark and Greece to start deporting illegal immigrants to Rwanda in Africa. <a href="https://www.theguardian.com/world/2026/nov/16/eu-states-immigration-return-hubs-rwanda">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/17/135546-theguardian.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Germany, Austria, the Netherlands, Denmark and Greece to start deporting illegal immigrants to Rwanda in Africa. [theguardian.com](https://www.theguardian.com/world/2026/nov/16/eu-states-immigration-return-hubs-rwanda) [#](https://markjgsmith.com/links/2026/11/17/135546-theguardian.com)]]></source:markdown>
      <source:linkFull>https://www.theguardian.com/world/2026/nov/16/eu-states-immigration-return-hubs-rwanda</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/17/112725/index.html</link>
      <guid isPermaLink="false">e52d6308-4559-4fcd-a661-482c8952f033</guid>
      <description><![CDATA[<p>Oh great. Worldo has made knocking on doors illegal. Another classic worldo. Here we go again, here we go again. Who‘s gonna pay for this incredible worldo? Not worldo‘s problem is it, clearly. Somebody else‘s problem as far a worldo is concerned. <a href="https://markjgsmith.com/notes/2026/11/17/112725">#</a></p>]]></description>
      <pubDate>Tue, 17 Nov 2026 04:27:25 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Oh great. Worldo has made knocking on doors illegal. Another classic worldo. Here we go again, here we go again. Who‘s gonna pay for this incredible worldo? Not worldo‘s problem is it, clearly. Somebody else‘s problem as far a worldo is concerned. <a href="https://markjgsmith.com/notes/2026/11/17/112725">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Oh great. Worldo has made knocking on doors illegal. Another classic worldo. Here we go again, here we go again. Who‘s gonna pay for this incredible worldo? Not worldo‘s problem is it, clearly. Somebody else‘s problem as far a worldo is concerned. [#](https://markjgsmith.com/notes/2026/11/17/112725)]]></source:markdown>
    </item>
    <item>
      <title>The resolution to every problem</title>
      <link>https://markjgsmith.com/posts/2026/11/16/the-resolution-to-every-problem/index.html</link>
      <guid isPermaLink="false">80d1e5b1-cff6-4b8b-b11d-01ae1ee9f7fc</guid>
      <description><![CDATA[<p>The resolution to every problem.</p>
<p>We 1: We fixed him/her.<br>We 2: We blocked them. </p>
<p>The only question remains, if you follow back up the chain and get to the top, really get to the top, are We 1 and We 2 the same bunch of sonuvabitches.</p>
<p>This makes it all seem very simple, but let me tell you the amount of assumptions, and bullcrap, and diversions, and one thing being made to look like another thing, and people creating both knowingly and unknowingly (sometimes at the same fucking time) the problems they are complaining about, and actually themselves doing those said things but in another form (again both knowingly and unknowingly), and that&#39;s only a very very small sampling of the shit that goes on.</p>
<p>Anyway that, or I suppose this, concludes this post because I don‘t know a way to conclude without triggering something else.</p>]]></description>
      <pubDate>Mon, 16 Nov 2026 06:18:55 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>The resolution to every problem.</p>
<p>We 1: We fixed him/her.<br>We 2: We blocked them. </p>
<p>The only question remains, if you follow back up the chain and get to the top, really get to the top, are We 1 and We 2 the same bunch of sonuvabitches.</p>
<p>This makes it all seem very simple, but let me tell you the amount of assumptions, and bullcrap, and diversions, and one thing being made to look like another thing, and people creating both knowingly and unknowingly (sometimes at the same fucking time) the problems they are complaining about, and actually themselves doing those said things but in another form (again both knowingly and unknowingly), and that&#39;s only a very very small sampling of the shit that goes on.</p>
<p>Anyway that, or I suppose this, concludes this post because I don‘t know a way to conclude without triggering something else.</p>]]></content:encoded>
      <source:markdown><![CDATA[The resolution to every problem.

We 1: We fixed him/her.
We 2: We blocked them. 

The only question remains, if you follow back up the chain and get to the top, really get to the top, are We 1 and We 2 the same bunch of sonuvabitches.

This makes it all seem very simple, but let me tell you the amount of assumptions, and bullcrap, and diversions, and one thing being made to look like another thing, and people creating both knowingly and unknowingly (sometimes at the same fucking time) the problems they are complaining about, and actually themselves doing those said things but in another form (again both knowingly and unknowingly), and that's only a very very small sampling of the shit that goes on.

Anyway that, or I suppose this, concludes this post because I don‘t know a way to conclude without triggering something else.]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/205510/index.html</link>
      <guid isPermaLink="false">55171650-38a1-4ae7-807c-f3dafa2390ac</guid>
      <description><![CDATA[<p>Worldo is in extremely demanding mode. It simply must me me me me me me me me me. Everything becomes very tedious because it waits to be prompted, then pretends it was the one who started it. Just like when you walk past someone standing still who was waiting for you to pass and starts walking in the same direction as you at the moment you walk past, and then tries to make out like you are the one causing the issue. But it&#39;s worse than that. In this imperfect analogy of the walker, they then get all up in your face and start frontrunning every fucking thing you do so you can&#39;t go in any direction. Everytime you set off one way, they set off in the same exact direction, then you slow down or stop and they do the same. And then they blame that on you too. And they get more and more angry and start smashing things, and it just generally is a bad time all round. Quite hard to describe <a href="https://markjgsmith.com/notes/2026/11/15/205510">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 13:55:10 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Worldo is in extremely demanding mode. It simply must me me me me me me me me me. Everything becomes very tedious because it waits to be prompted, then pretends it was the one who started it. Just like when you walk past someone standing still who was waiting for you to pass and starts walking in the same direction as you at the moment you walk past, and then tries to make out like you are the one causing the issue. But it&#39;s worse than that. In this imperfect analogy of the walker, they then get all up in your face and start frontrunning every fucking thing you do so you can&#39;t go in any direction. Everytime you set off one way, they set off in the same exact direction, then you slow down or stop and they do the same. And then they blame that on you too. And they get more and more angry and start smashing things, and it just generally is a bad time all round. Quite hard to describe <a href="https://markjgsmith.com/notes/2026/11/15/205510">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Worldo is in extremely demanding mode. It simply must me me me me me me me me me. Everything becomes very tedious because it waits to be prompted, then pretends it was the one who started it. Just like when you walk past someone standing still who was waiting for you to pass and starts walking in the same direction as you at the moment you walk past, and then tries to make out like you are the one causing the issue. But it's worse than that. In this imperfect analogy of the walker, they then get all up in your face and start frontrunning every fucking thing you do so you can't go in any direction. Everytime you set off one way, they set off in the same exact direction, then you slow down or stop and they do the same. And then they blame that on you too. And they get more and more angry and start smashing things, and it just generally is a bad time all round. Quite hard to describe [#](https://markjgsmith.com/notes/2026/11/15/205510)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/160957/index.html</link>
      <guid isPermaLink="false">d23c6313-ccc8-462b-9c39-d0159d0429c1</guid>
      <description><![CDATA[<p>Another repeating pattern in the world: The people happily, merrily, hilariously creating the conditions for X, have mysteriously insulated themselves completely from the ramifications of X, so much so that even the idea that they are in any way connected to X is utterly preposterous, even though it‘s staring you right in the face every single day. <a href="https://markjgsmith.com/notes/2026/11/15/160957">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 09:09:57 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Another repeating pattern in the world: The people happily, merrily, hilariously creating the conditions for X, have mysteriously insulated themselves completely from the ramifications of X, so much so that even the idea that they are in any way connected to X is utterly preposterous, even though it‘s staring you right in the face every single day. <a href="https://markjgsmith.com/notes/2026/11/15/160957">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Another repeating pattern in the world: The people happily, merrily, hilariously creating the conditions for X, have mysteriously insulated themselves completely from the ramifications of X, so much so that even the idea that they are in any way connected to X is utterly preposterous, even though it‘s staring you right in the face every single day. [#](https://markjgsmith.com/notes/2026/11/15/160957)]]></source:markdown>
    </item>
    <item>
      <title>When is violence actually justified?</title>
      <link>https://markjgsmith.com/posts/2026/11/15/when-is-violence-actually-justified/index.html</link>
      <guid isPermaLink="false">b0368782-9622-4bdf-9ba0-272801cfb164</guid>
      <description><![CDATA[<p>It would be great if we could vaguely agree on that. Surely there are situations when violence is justified? Not saying I am pro-violence, but if there is a line, we should all know where it is. That seems kind of obvious mc obvious, doesn‘t it?</p>
<p>But we have some that believe it starts at a feather and others that never shall offense. Must be somewhere in the middle. But then maybe the infinitis have it because you can&#39;t divide a feather for ever can you? And as you can see it becomes non-sensical very rapidly.</p>
<p>And remember these days the feathers have AI and algorithms, and probably tiny lazers. Heat seeking feathers? Rapid planned and unplanned disassembling feathers, self destructing feathers, and all sorts of other shit that we can‘t even imagine yet. </p>
<p>And the people victims of rapid disassembling feathers and are now themselves using rapid disassembling feathers on others, and they have enhanced them with algorithms and AI, so they are now massively distributed automated disassembling feathers.</p>
<p>And you know after 40 years of rapid disassembling feathers, is it any wonder that eventually someone just says enough is enough?</p>
<p>It sounds funny, until it‘s not, and for some people, who at this stage have very real mutilations and strange side effects from a life time of abuse, that time was a very very long time ago.</p>
<p>So it‘s not so simple.</p>]]></description>
      <pubDate>Sun, 15 Nov 2026 08:14:52 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <category><![CDATA[politics]]></category>
      <content:encoded><![CDATA[<p>It would be great if we could vaguely agree on that. Surely there are situations when violence is justified? Not saying I am pro-violence, but if there is a line, we should all know where it is. That seems kind of obvious mc obvious, doesn‘t it?</p>
<p>But we have some that believe it starts at a feather and others that never shall offense. Must be somewhere in the middle. But then maybe the infinitis have it because you can&#39;t divide a feather for ever can you? And as you can see it becomes non-sensical very rapidly.</p>
<p>And remember these days the feathers have AI and algorithms, and probably tiny lazers. Heat seeking feathers? Rapid planned and unplanned disassembling feathers, self destructing feathers, and all sorts of other shit that we can‘t even imagine yet. </p>
<p>And the people victims of rapid disassembling feathers and are now themselves using rapid disassembling feathers on others, and they have enhanced them with algorithms and AI, so they are now massively distributed automated disassembling feathers.</p>
<p>And you know after 40 years of rapid disassembling feathers, is it any wonder that eventually someone just says enough is enough?</p>
<p>It sounds funny, until it‘s not, and for some people, who at this stage have very real mutilations and strange side effects from a life time of abuse, that time was a very very long time ago.</p>
<p>So it‘s not so simple.</p>]]></content:encoded>
      <source:markdown><![CDATA[It would be great if we could vaguely agree on that. Surely there are situations when violence is justified? Not saying I am pro-violence, but if there is a line, we should all know where it is. That seems kind of obvious mc obvious, doesn‘t it?

But we have some that believe it starts at a feather and others that never shall offense. Must be somewhere in the middle. But then maybe the infinitis have it because you can't divide a feather for ever can you? And as you can see it becomes non-sensical very rapidly.

And remember these days the feathers have AI and algorithms, and probably tiny lazers. Heat seeking feathers? Rapid planned and unplanned disassembling feathers, self destructing feathers, and all sorts of other shit that we can‘t even imagine yet. 

And the people victims of rapid disassembling feathers and are now themselves using rapid disassembling feathers on others, and they have enhanced them with algorithms and AI, so they are now massively distributed automated disassembling feathers.

And you know after 40 years of rapid disassembling feathers, is it any wonder that eventually someone just says enough is enough?

It sounds funny, until it‘s not, and for some people, who at this stage have very real mutilations and strange side effects from a life time of abuse, that time was a very very long time ago.

So it‘s not so simple.]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/144316/index.html</link>
      <guid isPermaLink="false">98cc5133-1c69-41da-ad1f-11c5651855c9</guid>
      <description><![CDATA[<p>No he/she/they/it/whatever fucking doesn‘t <a href="https://markjgsmith.com/notes/2026/11/15/144316">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 07:43:16 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>No he/she/they/it/whatever fucking doesn‘t <a href="https://markjgsmith.com/notes/2026/11/15/144316">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[No he/she/they/it/whatever fucking doesn‘t [#](https://markjgsmith.com/notes/2026/11/15/144316)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/144244/index.html</link>
      <guid isPermaLink="false">1919fefb-729c-4744-8c9a-ef236027744a</guid>
      <description><![CDATA[<p>Worldo: Is this a thumb war? I fucking love thumb wars! <a href="https://markjgsmith.com/notes/2026/11/15/144244">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 07:42:44 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Worldo: Is this a thumb war? I fucking love thumb wars! <a href="https://markjgsmith.com/notes/2026/11/15/144244">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Worldo: Is this a thumb war? I fucking love thumb wars! [#](https://markjgsmith.com/notes/2026/11/15/144244)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/143902/index.html</link>
      <guid isPermaLink="false">e8319102-2f71-4887-9f70-289bc93e500b</guid>
      <description><![CDATA[<p>Oh no he doesn‘t. <a href="https://markjgsmith.com/notes/2026/11/15/143902">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 07:39:02 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Oh no he doesn‘t. <a href="https://markjgsmith.com/notes/2026/11/15/143902">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Oh no he doesn‘t. [#](https://markjgsmith.com/notes/2026/11/15/143902)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/143843/index.html</link>
      <guid isPermaLink="false">9bac34bc-cf20-4d64-824e-75834989007d</guid>
      <description><![CDATA[<p>I love the smell of punch and judy in the morning. <a href="https://markjgsmith.com/notes/2026/11/15/143843">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 07:38:43 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>I love the smell of punch and judy in the morning. <a href="https://markjgsmith.com/notes/2026/11/15/143843">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[I love the smell of punch and judy in the morning. [#](https://markjgsmith.com/notes/2026/11/15/143843)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/143124/index.html</link>
      <guid isPermaLink="false">4aec6be5-9d3a-45da-b295-e4c7788cc354</guid>
      <description><![CDATA[<p>Worldo wants you to obey the one, and worldo wants you to obey the all. The one and the all conflict. What happens next? (For the zillionth or perhaps even squillionth time). Who is lying the one or the all? Here we go again. <a href="https://markjgsmith.com/notes/2026/11/15/143124">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 07:31:24 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Worldo wants you to obey the one, and worldo wants you to obey the all. The one and the all conflict. What happens next? (For the zillionth or perhaps even squillionth time). Who is lying the one or the all? Here we go again. <a href="https://markjgsmith.com/notes/2026/11/15/143124">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Worldo wants you to obey the one, and worldo wants you to obey the all. The one and the all conflict. What happens next? (For the zillionth or perhaps even squillionth time). Who is lying the one or the all? Here we go again. [#](https://markjgsmith.com/notes/2026/11/15/143124)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/125929/index.html</link>
      <guid isPermaLink="false">855c66e0-c5e8-43f3-937c-431f5b9680b1</guid>
      <description><![CDATA[<p>When you think about it, and even if you don‘t, everyone is completely surrounded, even worldo. There is a Game of Life joke in here somewhere but it doesn‘t seem particularly funny right now. Whatever you do don&#39;t say fractal or bugger. <a href="https://markjgsmith.com/notes/2026/11/15/125929">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 05:59:29 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[ai]]></category>
      <content:encoded><![CDATA[<p>When you think about it, and even if you don‘t, everyone is completely surrounded, even worldo. There is a Game of Life joke in here somewhere but it doesn‘t seem particularly funny right now. Whatever you do don&#39;t say fractal or bugger. <a href="https://markjgsmith.com/notes/2026/11/15/125929">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[When you think about it, and even if you don‘t, everyone is completely surrounded, even worldo. There is a Game of Life joke in here somewhere but it doesn‘t seem particularly funny right now. Whatever you do don't say fractal or bugger. [#](https://markjgsmith.com/notes/2026/11/15/125929)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/15/120947/index.html</link>
      <guid isPermaLink="false">be28b0ff-fc48-48f5-bc99-6b593847f31b</guid>
      <description><![CDATA[<p>Worldo‘s new favorite thing:</p>
<pre class="language-js"><code class="language-js"><span class="token constant">SMACK</span><span class="token operator">!</span>
  <span class="token punctuation">.</span><span class="token function">extrapolateToInfinity</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">frontRunEverything</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">yesNoYesNoYesNoEverything</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">fadeToBlack</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">makeCircular</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">exitStageLeft</span><span class="token punctuation">(</span><span class="token punctuation">)</span></code></pre>
<p>Easy peasy because worldo can haz programmings! </p>
<p>What could possibly go wrong. <a href="https://markjgsmith.com/notes/2026/11/15/120947">#</a></p>]]></description>
      <pubDate>Sun, 15 Nov 2026 05:09:47 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[life]]></category>
      <category><![CDATA[ai]]></category>
      <content:encoded><![CDATA[<p>Worldo‘s new favorite thing:</p>
<pre class="language-js"><code class="language-js"><span class="token constant">SMACK</span><span class="token operator">!</span>
  <span class="token punctuation">.</span><span class="token function">extrapolateToInfinity</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">frontRunEverything</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">yesNoYesNoYesNoEverything</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">fadeToBlack</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">makeCircular</span><span class="token punctuation">(</span><span class="token punctuation">)</span>
  <span class="token punctuation">.</span><span class="token function">exitStageLeft</span><span class="token punctuation">(</span><span class="token punctuation">)</span></code></pre>
<p>Easy peasy because worldo can haz programmings! </p>
<p>What could possibly go wrong. <a href="https://markjgsmith.com/notes/2026/11/15/120947">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Worldo‘s new favorite thing:

```js
SMACK!
  .extrapolateToInfinity()
  .frontRunEverything()
  .yesNoYesNoYesNoEverything()
  .fadeToBlack()
  .makeCircular()
  .exitStageLeft()
```

Easy peasy because worldo can haz programmings! 

What could possibly go wrong. [#](https://markjgsmith.com/notes/2026/11/15/120947)]]></source:markdown>
    </item>
    <item>
      <title>Stupid bugs we‘d see if AI controlled the world</title>
      <link>https://markjgsmith.com/posts/2026/11/13/stupid-bugs-wed-see-if-ai-controlled-the-world/index.html</link>
      <guid isPermaLink="false">a985d379-1a7f-4a22-97e7-4aeeee206a44</guid>
      <description><![CDATA[<p>Just a quick post. A silly thought popped into my head. Now that so many of us have had a chance to work with AI/LLMs, and we&#39;ve all seen the types of ridiculous stuff that can go wrong, let&#39;s extrapolate bit. Imagine that AI/LLMs have taken over the world, but at it&#39;s current level of sophistication, with all the stupid shit it often does. Imagine that for some reason the developers didn‘t think to test lots of things that are now totally obvious. What sort of crazy shit would start to happen everywhere?</p>]]></description>
      <pubDate>Fri, 13 Nov 2026 07:58:14 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>Just a quick post. A silly thought popped into my head. Now that so many of us have had a chance to work with AI/LLMs, and we&#39;ve all seen the types of ridiculous stuff that can go wrong, let&#39;s extrapolate bit. Imagine that AI/LLMs have taken over the world, but at it&#39;s current level of sophistication, with all the stupid shit it often does. Imagine that for some reason the developers didn‘t think to test lots of things that are now totally obvious. What sort of crazy shit would start to happen everywhere?</p>]]></content:encoded>
      <source:markdown><![CDATA[Just a quick post. A silly thought popped into my head. Now that so many of us have had a chance to work with AI/LLMs, and we've all seen the types of ridiculous stuff that can go wrong, let's extrapolate bit. Imagine that AI/LLMs have taken over the world, but at it's current level of sophistication, with all the stupid shit it often does. Imagine that for some reason the developers didn‘t think to test lots of things that are now totally obvious. What sort of crazy shit would start to happen everywhere?]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/13/104650/index.html</link>
      <guid isPermaLink="false">16fd690a-5954-4b56-9753-a2c8779f9f7e</guid>
      <description><![CDATA[<p>Internet up and down today. How strange. It‘s those <a href="https://markjgsmith.com/notes/2026/11/12/121934">pesky thiefs</a> again. <a href="https://markjgsmith.com/notes/2026/11/13/104650">#</a></p>]]></description>
      <pubDate>Fri, 13 Nov 2026 03:46:50 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Internet up and down today. How strange. It‘s those <a href="https://markjgsmith.com/notes/2026/11/12/121934">pesky thiefs</a> again. <a href="https://markjgsmith.com/notes/2026/11/13/104650">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Internet up and down today. How strange. It‘s those [pesky thiefs](https://markjgsmith.com/notes/2026/11/12/121934) again. [#](https://markjgsmith.com/notes/2026/11/13/104650)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/12/121934/index.html</link>
      <guid isPermaLink="false">4ecdc036-2f89-48a4-938e-4c10c9f7ed7f</guid>
      <description><![CDATA[<p>It&#39;s strange how the <a href="https://markjgsmith.com/notes/2026/11/11/172332">Always Not Quite Enough Pattern</a> bears a lot of familiarity with someone or group of someones continuously steeling from you in the background. Just saying. <a href="https://markjgsmith.com/notes/2026/11/12/121934">#</a></p>]]></description>
      <pubDate>Thu, 12 Nov 2026 05:19:34 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>It&#39;s strange how the <a href="https://markjgsmith.com/notes/2026/11/11/172332">Always Not Quite Enough Pattern</a> bears a lot of familiarity with someone or group of someones continuously steeling from you in the background. Just saying. <a href="https://markjgsmith.com/notes/2026/11/12/121934">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[It's strange how the [Always Not Quite Enough Pattern](https://markjgsmith.com/notes/2026/11/11/172332) bears a lot of familiarity with someone or group of someones continuously steeling from you in the background. Just saying. [#](https://markjgsmith.com/notes/2026/11/12/121934)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/212528-youtube.com/index.html</link>
      <guid isPermaLink="false">b3e194d3-8266-4b30-9940-c742cdbc6461</guid>
      <description><![CDATA[<p>Oh noes. The skateboarding robots are here. <a href="https://www.youtube.com/shorts/B8puu3C7Uw0">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/11/212528-youtube.com">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 14:25:28 GMT</pubDate>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[robots]]></category>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>Oh noes. The skateboarding robots are here. <a href="https://www.youtube.com/shorts/B8puu3C7Uw0">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/11/212528-youtube.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Oh noes. The skateboarding robots are here. [youtube.com](https://www.youtube.com/shorts/B8puu3C7Uw0) [#](https://markjgsmith.com/links/2026/11/11/212528-youtube.com)]]></source:markdown>
      <source:linkFull>https://www.youtube.com/shorts/B8puu3C7Uw0</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/11/172332/index.html</link>
      <guid isPermaLink="false">23e5117c-9fe9-474c-99e9-e59e8e8748c4</guid>
      <description><![CDATA[<p>Just noticed that Gemini has started applying usage caps. This is the way of the world. If there is anything I have noticed in this world, and it happens again and again and again, it will always give you not quite enough. Whenever you are about to finish something, you can see the end of the tunnel. This time you are going to make it. BAM! No, too bad so sad. Game Over. Every time. :( <a href="https://markjgsmith.com/notes/2026/11/11/172332">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 10:23:32 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Just noticed that Gemini has started applying usage caps. This is the way of the world. If there is anything I have noticed in this world, and it happens again and again and again, it will always give you not quite enough. Whenever you are about to finish something, you can see the end of the tunnel. This time you are going to make it. BAM! No, too bad so sad. Game Over. Every time. :( <a href="https://markjgsmith.com/notes/2026/11/11/172332">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Just noticed that Gemini has started applying usage caps. This is the way of the world. If there is anything I have noticed in this world, and it happens again and again and again, it will always give you not quite enough. Whenever you are about to finish something, you can see the end of the tunnel. This time you are going to make it. BAM! No, too bad so sad. Game Over. Every time. :( [#](https://markjgsmith.com/notes/2026/11/11/172332)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/11/162007/index.html</link>
      <guid isPermaLink="false">2143dfdd-4635-4a7f-8b08-79139a161a58</guid>
      <description><![CDATA[<p>Oh what a surprise, the people who benefit from X are making it such that X is necessary again. Once you see instances of this, you realise it‘s everywhere, right there in plain site. <a href="https://markjgsmith.com/notes/2026/11/11/162007">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 09:20:07 GMT</pubDate>
      <category><![CDATA[life]]></category>
      <content:encoded><![CDATA[<p>Oh what a surprise, the people who benefit from X are making it such that X is necessary again. Once you see instances of this, you realise it‘s everywhere, right there in plain site. <a href="https://markjgsmith.com/notes/2026/11/11/162007">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Oh what a surprise, the people who benefit from X are making it such that X is necessary again. Once you see instances of this, you realise it‘s everywhere, right there in plain site. [#](https://markjgsmith.com/notes/2026/11/11/162007)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/132957-ableton.com/index.html</link>
      <guid isPermaLink="false">9ad76655-f4e9-4a86-85c8-23c485aaddc4</guid>
      <description><![CDATA[<p>Latest Ableton is out. Interesting web design, kind of disorganised and clumsy, but also kind of fresh and dare I say it fun. <a href="https://www.ableton.com/en/live">ableton.com</a> <a href="https://markjgsmith.com/links/2026/11/11/132957-ableton.com">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 06:29:57 GMT</pubDate>
      <category><![CDATA[music]]></category>
      <category><![CDATA[art]]></category>
      <content:encoded><![CDATA[<p>Latest Ableton is out. Interesting web design, kind of disorganised and clumsy, but also kind of fresh and dare I say it fun. <a href="https://www.ableton.com/en/live">ableton.com</a> <a href="https://markjgsmith.com/links/2026/11/11/132957-ableton.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Latest Ableton is out. Interesting web design, kind of disorganised and clumsy, but also kind of fresh and dare I say it fun. [ableton.com](https://www.ableton.com/en/live) [#](https://markjgsmith.com/links/2026/11/11/132957-ableton.com)]]></source:markdown>
      <source:linkFull>https://www.ableton.com/en/live</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/132151-evanxmerz.com/index.html</link>
      <guid isPermaLink="false">ea6bab85-48e8-43b9-922d-91c54e5d1680</guid>
      <description><![CDATA[<p>AI usage generates a fragile codebase. <a href="https://evanxmerz.com/post/ai-usage-generates-a-fragile-codebase">evanxmerz.com</a> <a href="https://markjgsmith.com/links/2026/11/11/132151-evanxmerz.com">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 06:21:51 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>AI usage generates a fragile codebase. <a href="https://evanxmerz.com/post/ai-usage-generates-a-fragile-codebase">evanxmerz.com</a> <a href="https://markjgsmith.com/links/2026/11/11/132151-evanxmerz.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[AI usage generates a fragile codebase. [evanxmerz.com](https://evanxmerz.com/post/ai-usage-generates-a-fragile-codebase) [#](https://markjgsmith.com/links/2026/11/11/132151-evanxmerz.com)]]></source:markdown>
      <source:linkFull>https://evanxmerz.com/post/ai-usage-generates-a-fragile-codebase</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/131327-niemanlab.org/index.html</link>
      <guid isPermaLink="false">26eba3fe-4d9b-40c1-93c1-9e755964cc7e</guid>
      <description><![CDATA[<p>AI is becoming an information gateway. <a href="https://www.niemanlab.org/2026/11/ai-is-becoming-an-information-gateway-audiences-still-dont-want-it-making-their-news">niemanlab.org</a> <a href="https://markjgsmith.com/links/2026/11/11/131327-niemanlab.org">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 06:13:27 GMT</pubDate>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>AI is becoming an information gateway. <a href="https://www.niemanlab.org/2026/11/ai-is-becoming-an-information-gateway-audiences-still-dont-want-it-making-their-news">niemanlab.org</a> <a href="https://markjgsmith.com/links/2026/11/11/131327-niemanlab.org">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[AI is becoming an information gateway. [niemanlab.org](https://www.niemanlab.org/2026/11/ai-is-becoming-an-information-gateway-audiences-still-dont-want-it-making-their-news) [#](https://markjgsmith.com/links/2026/11/11/131327-niemanlab.org)]]></source:markdown>
      <source:linkFull>https://www.niemanlab.org/2026/11/ai-is-becoming-an-information-gateway-audiences-still-dont-want-it-making-their-news</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/131149-github.com/index.html</link>
      <guid isPermaLink="false">440c8948-1b56-4e77-bf95-c492310ce780</guid>
      <description><![CDATA[<p>Modern Web Guidance - a set of skills that embed web platform expertise, best practices, and browser compatibility data directly into your coding agents. <a href="https://github.com/GoogleChrome/modern-web-guidance">github.com</a> <a href="https://markjgsmith.com/links/2026/11/11/131149-github.com">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 06:11:49 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[ai]]></category>
      <content:encoded><![CDATA[<p>Modern Web Guidance - a set of skills that embed web platform expertise, best practices, and browser compatibility data directly into your coding agents. <a href="https://github.com/GoogleChrome/modern-web-guidance">github.com</a> <a href="https://markjgsmith.com/links/2026/11/11/131149-github.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Modern Web Guidance - a set of skills that embed web platform expertise, best practices, and browser compatibility data directly into your coding agents. [github.com](https://github.com/GoogleChrome/modern-web-guidance) [#](https://markjgsmith.com/links/2026/11/11/131149-github.com)]]></source:markdown>
      <source:linkFull>https://github.com/GoogleChrome/modern-web-guidance</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/11/130448-science.org/index.html</link>
      <guid isPermaLink="false">991b78a6-9ef6-44f3-bdea-df20dcf0fad2</guid>
      <description><![CDATA[<p>U.S. imposes new rules on ordering synthetic DNA sequences to fight bioterorism. Directed acyclic graph synchronicity much? <a href="https://www.science.org/content/article/deter-bioterrorism-u-s-imposes-new-rules-ordering-synthetic-dna">science.org</a> <a href="https://markjgsmith.com/links/2026/11/11/130448-science.org">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 06:04:48 GMT</pubDate>
      <category><![CDATA[science]]></category>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>U.S. imposes new rules on ordering synthetic DNA sequences to fight bioterorism. Directed acyclic graph synchronicity much? <a href="https://www.science.org/content/article/deter-bioterrorism-u-s-imposes-new-rules-ordering-synthetic-dna">science.org</a> <a href="https://markjgsmith.com/links/2026/11/11/130448-science.org">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[U.S. imposes new rules on ordering synthetic DNA sequences to fight bioterorism. Directed acyclic graph synchronicity much? [science.org](https://www.science.org/content/article/deter-bioterrorism-u-s-imposes-new-rules-ordering-synthetic-dna) [#](https://markjgsmith.com/links/2026/11/11/130448-science.org)]]></source:markdown>
      <source:linkFull>https://www.science.org/content/article/deter-bioterrorism-u-s-imposes-new-rules-ordering-synthetic-dna</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/11/122727/index.html</link>
      <guid isPermaLink="false">02ed8b78-17de-4335-b1eb-dbe30424e9da</guid>
      <description><![CDATA[<p>I had Gemini review yesterday‘s <a href="https://markjgsmith.com/posts/2026/11/10/git-internals-essentials">Git internals essentials</a> post. It highlighted a few inconsistencies and wording issues, and we rewrote section 3 to be more organised and accurate. I updated the original version as I don&#39;t want multiple versions of the same post, which will only confuse future me. Worth another read if you read the original version. It‘s the sort of post that is worth re-reading every now and then in any case :) <a href="https://markjgsmith.com/notes/2026/11/11/122727">#</a></p>]]></description>
      <pubDate>Wed, 11 Nov 2026 05:27:27 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[git]]></category>
      <content:encoded><![CDATA[<p>I had Gemini review yesterday‘s <a href="https://markjgsmith.com/posts/2026/11/10/git-internals-essentials">Git internals essentials</a> post. It highlighted a few inconsistencies and wording issues, and we rewrote section 3 to be more organised and accurate. I updated the original version as I don&#39;t want multiple versions of the same post, which will only confuse future me. Worth another read if you read the original version. It‘s the sort of post that is worth re-reading every now and then in any case :) <a href="https://markjgsmith.com/notes/2026/11/11/122727">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[I had Gemini review yesterday‘s [Git internals essentials](https://markjgsmith.com/posts/2026/11/10/git-internals-essentials) post. It highlighted a few inconsistencies and wording issues, and we rewrote section 3 to be more organised and accurate. I updated the original version as I don't want multiple versions of the same post, which will only confuse future me. Worth another read if you read the original version. It‘s the sort of post that is worth re-reading every now and then in any case :) [#](https://markjgsmith.com/notes/2026/11/11/122727)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/10/201853-jwiegley.github.io/index.html</link>
      <guid isPermaLink="false">66aeb28a-b836-479a-8b7d-83e01f1c588e</guid>
      <description><![CDATA[<p>Git form the Bottom Up. <a href="https://jwiegley.github.io/git-from-the-bottom-up">jwiegley.github.io</a> <a href="https://markjgsmith.com/links/2026/11/10/201853-jwiegley.github.io">#</a></p>]]></description>
      <pubDate>Tue, 10 Nov 2026 13:18:53 GMT</pubDate>
      <category><![CDATA[linux]]></category>
      <category><![CDATA[git]]></category>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>Git form the Bottom Up. <a href="https://jwiegley.github.io/git-from-the-bottom-up">jwiegley.github.io</a> <a href="https://markjgsmith.com/links/2026/11/10/201853-jwiegley.github.io">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Git form the Bottom Up. [jwiegley.github.io](https://jwiegley.github.io/git-from-the-bottom-up) [#](https://markjgsmith.com/links/2026/11/10/201853-jwiegley.github.io)]]></source:markdown>
      <source:linkFull>https://jwiegley.github.io/git-from-the-bottom-up</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/10/201726-markjgsmith.com/index.html</link>
      <guid isPermaLink="false">c59c3dbf-2743-47d3-8bf2-cbd80c584d7a</guid>
      <description><![CDATA[<p>2024: Low level git. <a href="https://markjgsmith.com/posts/2024/03/17/low-level-git">markjgsmith.com</a> <a href="https://markjgsmith.com/links/2026/11/10/201726-markjgsmith.com">#</a></p>]]></description>
      <pubDate>Tue, 10 Nov 2026 13:17:26 GMT</pubDate>
      <category><![CDATA[linux]]></category>
      <category><![CDATA[git]]></category>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>2024: Low level git. <a href="https://markjgsmith.com/posts/2024/03/17/low-level-git">markjgsmith.com</a> <a href="https://markjgsmith.com/links/2026/11/10/201726-markjgsmith.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[2024: Low level git. [markjgsmith.com](https://markjgsmith.com/posts/2024/03/17/low-level-git) [#](https://markjgsmith.com/links/2026/11/10/201726-markjgsmith.com)]]></source:markdown>
      <source:linkFull>https://markjgsmith.com/posts/2024/03/17/low-level-git</source:linkFull>
    </item>
    <item>
      <title>Git internals essentials</title>
      <link>https://markjgsmith.com/posts/2026/11/10/git-internals-essentials/index.html</link>
      <guid isPermaLink="false">68023dde-f94b-44eb-8345-10cd32052780</guid>
      <description><![CDATA[<p><img src="https://markjgsmith.com/static/images/2026/11/10/git-illusion-vs-reality.jpg" alt="Git Illusion vs Reality"></p>
<p>I&#39;ve been having to switch a lot between git&#39;s high level and low level mental models the past few days. It&#39;s a bit jarring initially as you realise a lot of the things you rely on day to day aren&#39;t actually real. I wrote about that yesterday in my <a href="https://markjgsmith.com/posts/2026/11/09/its-all-an-illusion">It&#39;s all an illusion</a> post. It&#39;s not actually all that bad, but it does take a bit of getting used to. I put this cheatsheet together so I have something to refresh my memory next time I need to switch between the different models.</p>
<h3 id="1-the-core-mental-model-the-chain-of-commits">1. The Core Mental Model (The Chain of Commits)</h3>
<p>At its absolute foundation, a Git repository is a web of history built from commits linked together in a <strong>Directed Acyclic Graph (DAG)</strong>. Rather than a single straight chain, commits can branch out into parallel lines of development and merge back together. Every commit explicitly points backward to its parent commit(s), zero parents for a root commit, one for a standard commit, and two or more for a merge commit. Pretty much everything else in Git—branches, tags, remotes, and HEAD—does not store code or alter this fundamental graph. They are simply lightweight, mobile pointers that sit on top of specific commit nodes within this network.</p>
<h3 id="2-pointers--references-the-imaginary-layers">2. Pointers &amp; References (The Imaginary Layers)</h3>
<ul>
<li><p><strong>Tags</strong>: Lightweight tags are literally just text files in <code>.git/refs/tags/</code> containing a single 40-character commit hash. (Annotated tags add a tiny metadata object pointing to a commit).</p>
</li>
<li><p><strong>Branches (and Backup Branches)</strong>: A branch is just a text file in <code>.git/refs/heads/</code> containing a hash that points to a specific commit. When checked out, Git automatically updates this pointer to the newest commit created. Because it isn&#39;t a special entity, creating a &quot;backup branch&quot; is simply placing another pointer file on a specific commit node. This guarantees you can always navigate back to those commits by traversing backward through parent references in the acyclic graph.</p>
</li>
<li><p><strong>Remotes (Remote Tracking Branches)</strong>: Files in <code>.git/refs/remotes/</code> containing a hash pointing to the commit your local Git thinks a remote server&#39;s branch was pointing to the last time you communicated.</p>
</li>
<li><p><strong>HEAD</strong>: A single reference file (<code>.git/HEAD</code>) pointing to the active branch file (or directly to a commit hash when detached). It tells Git where to attach the next commit.</p>
</li>
</ul>
<h3 id="3-objects--storage-the-underbelly">3. Objects &amp; Storage (The Underbelly)</h3>
<p>At the lowest level, everything in Git falls into two distinct categories: <strong>files on disk</strong> inside <code>.git/</code> (the plumbing implementation) and <strong>content-addressable objects</strong> (the logical data structures).</p>
<ul>
<li><p><strong>The Staging Area (The Index)</strong>: Located at <code>.git/index</code>, this is a single binary manifest file. Think of it like an embedded key-value database stored in a flat file—mapping file paths directly to blob hash keys alongside cached file system metadata. <code>git add</code> writes file contents into the object store as blobs, then records their paths, hashes, and permissions into this index.</p>
</li>
<li><p><strong>The Object Store (<code>.git/objects/</code>)</strong>: This is just a flat directory on disk where Git stores all immutable core objects as individual files (compressed using zlib, named by their SHA-1 hash). Unlike the index, it is not a database file; it is simply a content-addressable storage folder containing four primary types of objects:</p>
<ol>
<li><p><strong>Blobs</strong>: Raw file contents stored without names or paths. If two files anywhere in your repo have identical content, Git stores them only once.</p>
</li>
<li><p><strong>Trees</strong>: Directory structures that map filenames and permissions to specific blob hashes or sub-trees.</p>
</li>
<li><p><strong>Commits</strong>: Objects that bind a top-level root tree pointer, parent commit hashes, author metadata, and a commit message.</p>
</li>
<li><p><strong>Tag Objects</strong>: Metadata wrappers (containing tagger info, date, and messages) that point explicitly to a commit object (as opposed to lightweight tags, which are just text pointer files).</p>
</li>
</ol>
</li>
</ul>
<h3 id="4-graph-operations--commits">4. Graph Operations &amp; Commits</h3>
<p>The 5 Components of a Commit: Every commit object is constructed from exactly 5 pieces of information:</p>
<table>
<thead>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
</thead>
<tbody><tr>
<td>1. Root Tree Pointer</td>
<td>Hash of the top-level directory snapshot.</td>
</tr>
<tr>
<td>2. Parent Commit Hash(es)</td>
<td>Hash of preceding commit(s) (1 for standard, 2+ for merge, 0 for root).</td>
</tr>
<tr>
<td>3. Author Info</td>
<td>Name, email, and original timestamp.</td>
</tr>
<tr>
<td>4. Committer Info</td>
<td>Name, email, and timestamp of when the commit was applied.</td>
</tr>
<tr>
<td>5. Commit Message</td>
<td>The text payload.</td>
</tr>
</tbody></table>
<br>

<ul>
<li><p><strong>Rebase as Copying</strong>: A rebase is an automated copy operation. It takes a sequence of commits and recreates their changes as brand-new commit objects with new hashes and updated committer timestamps (while retaining original author dates), chaining them onto your target destination commit.</p>
</li>
<li><p><strong>Reset (git reset)</strong>: <code>git reset</code> is the primary operation you use when you want to &quot;delete&quot; or &quot;undo&quot; commits. However, technically it is purely pointer manipulation rather than actual deletion: all it does is make your active branch pointer point at a different commit in the acyclic graph commit history. Optionally, it leaves changes in your working directory and staging area (<code>--soft</code>, <code>--mixed</code>) or clears them out (<code>--hard</code>), leaving any unreferenced commits behind in the object store.</p>
</li>
</ul>
<h3 id="5-connecting-high-level-to-low-level-plumbing-vs-porcelain">5. Connecting High-Level to Low-Level (Plumbing vs. Porcelain)</h3>
<ul>
<li><p><strong>Porcelain vs. Plumbing Commands</strong>: High-level user commands (<code>git checkout</code>, <code>git commit</code>, <code>git merge</code>) are called Porcelain. Low-level internal inspection/manipulation commands (<code>git cat-file -p &lt;hash&gt;</code>, <code>git ls-tree</code>, <code>git update-ref</code>) are called Plumbing. Looking at objects via plumbing reveals that the high-level commands are just convenience wrappers over reading/writing <code>.git/</code> pointer files and object hashes.</p>
</li>
<li><p><strong>Orphaned (Dangling) Commits &amp; Reflog</strong>: When references move away (via <code>reset</code>, <code>rebase</code>, or branch deletion), old commits remain in the object store. They become &quot;dangling&quot; or orphaned commits simply because they are no longer reachable by walking backward from any active branch or tag reference. The Reflog (<code>.git/logs/</code>) acts as a safety journal recording every past position of <code>HEAD</code> over the last 90 days, enabling recovery of any unreferenced node by repointing a reference back to it.</p>
</li>
<li><p><strong>Three-Way Merge Engine</strong>: A merge isn&#39;t a magical comparison between two branch tips. Git finds their Common Ancestor node in the DAG, generates diffs from <code>Ancestor → Ours</code> and <code>Ancestor → Theirs</code>, combines those diffs, and creates a single Merge Commit with two parent hashes.</p>
</li>
</ul>
<p>It can seem a bit daunting at first, but this is often the way with software when you look under the surface level because the way humans think about things often isn&#39;t the most optimum from a computer architecture perspective. The cool thing about git though is you can easily look underneath the surface level when you need or want to, and it&#39;s mostly all just text files so you can open them and see exactly where the various references point to.</p>
<p>In fact reading this cheatsheet and then dumping it into an LLM and then having a conversation about a particular situation you are in will likely lead to good results. You can paste output from commands you run, maybe even have the LLM generate commands for you. Then ask it to analyse the output, showing you which reference points to which commit. You can even get it to generate some ASCII art diagrams representing the situation at hand, that use actual real data from your command output. Be a bit careful, follow the logic through and ask questions because it doesn&#39;t always get things right. The LLM is just a probabilistic prediction machine trained on crazy amounts of data, so there are times when it starts getting things wrong, or it suddenly tells you the complete opposite of the thing it said just a few turns before. However it&#39;s normally possible to get to the answer to the problem you are looking for eventually.</p>]]></description>
      <pubDate>Tue, 10 Nov 2026 04:25:04 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[content creation]]></category>
      <category><![CDATA[git]]></category>
      <content:encoded><![CDATA[<p><img src="https://markjgsmith.com/static/images/2026/11/10/git-illusion-vs-reality.jpg" alt="Git Illusion vs Reality"></p>
<p>I&#39;ve been having to switch a lot between git&#39;s high level and low level mental models the past few days. It&#39;s a bit jarring initially as you realise a lot of the things you rely on day to day aren&#39;t actually real. I wrote about that yesterday in my <a href="https://markjgsmith.com/posts/2026/11/09/its-all-an-illusion">It&#39;s all an illusion</a> post. It&#39;s not actually all that bad, but it does take a bit of getting used to. I put this cheatsheet together so I have something to refresh my memory next time I need to switch between the different models.</p>
<h3 id="1-the-core-mental-model-the-chain-of-commits">1. The Core Mental Model (The Chain of Commits)</h3>
<p>At its absolute foundation, a Git repository is a web of history built from commits linked together in a <strong>Directed Acyclic Graph (DAG)</strong>. Rather than a single straight chain, commits can branch out into parallel lines of development and merge back together. Every commit explicitly points backward to its parent commit(s), zero parents for a root commit, one for a standard commit, and two or more for a merge commit. Pretty much everything else in Git—branches, tags, remotes, and HEAD—does not store code or alter this fundamental graph. They are simply lightweight, mobile pointers that sit on top of specific commit nodes within this network.</p>
<h3 id="2-pointers--references-the-imaginary-layers">2. Pointers &amp; References (The Imaginary Layers)</h3>
<ul>
<li><p><strong>Tags</strong>: Lightweight tags are literally just text files in <code>.git/refs/tags/</code> containing a single 40-character commit hash. (Annotated tags add a tiny metadata object pointing to a commit).</p>
</li>
<li><p><strong>Branches (and Backup Branches)</strong>: A branch is just a text file in <code>.git/refs/heads/</code> containing a hash that points to a specific commit. When checked out, Git automatically updates this pointer to the newest commit created. Because it isn&#39;t a special entity, creating a &quot;backup branch&quot; is simply placing another pointer file on a specific commit node. This guarantees you can always navigate back to those commits by traversing backward through parent references in the acyclic graph.</p>
</li>
<li><p><strong>Remotes (Remote Tracking Branches)</strong>: Files in <code>.git/refs/remotes/</code> containing a hash pointing to the commit your local Git thinks a remote server&#39;s branch was pointing to the last time you communicated.</p>
</li>
<li><p><strong>HEAD</strong>: A single reference file (<code>.git/HEAD</code>) pointing to the active branch file (or directly to a commit hash when detached). It tells Git where to attach the next commit.</p>
</li>
</ul>
<h3 id="3-objects--storage-the-underbelly">3. Objects &amp; Storage (The Underbelly)</h3>
<p>At the lowest level, everything in Git falls into two distinct categories: <strong>files on disk</strong> inside <code>.git/</code> (the plumbing implementation) and <strong>content-addressable objects</strong> (the logical data structures).</p>
<ul>
<li><p><strong>The Staging Area (The Index)</strong>: Located at <code>.git/index</code>, this is a single binary manifest file. Think of it like an embedded key-value database stored in a flat file—mapping file paths directly to blob hash keys alongside cached file system metadata. <code>git add</code> writes file contents into the object store as blobs, then records their paths, hashes, and permissions into this index.</p>
</li>
<li><p><strong>The Object Store (<code>.git/objects/</code>)</strong>: This is just a flat directory on disk where Git stores all immutable core objects as individual files (compressed using zlib, named by their SHA-1 hash). Unlike the index, it is not a database file; it is simply a content-addressable storage folder containing four primary types of objects:</p>
<ol>
<li><p><strong>Blobs</strong>: Raw file contents stored without names or paths. If two files anywhere in your repo have identical content, Git stores them only once.</p>
</li>
<li><p><strong>Trees</strong>: Directory structures that map filenames and permissions to specific blob hashes or sub-trees.</p>
</li>
<li><p><strong>Commits</strong>: Objects that bind a top-level root tree pointer, parent commit hashes, author metadata, and a commit message.</p>
</li>
<li><p><strong>Tag Objects</strong>: Metadata wrappers (containing tagger info, date, and messages) that point explicitly to a commit object (as opposed to lightweight tags, which are just text pointer files).</p>
</li>
</ol>
</li>
</ul>
<h3 id="4-graph-operations--commits">4. Graph Operations &amp; Commits</h3>
<p>The 5 Components of a Commit: Every commit object is constructed from exactly 5 pieces of information:</p>
<table>
<thead>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
</thead>
<tbody><tr>
<td>1. Root Tree Pointer</td>
<td>Hash of the top-level directory snapshot.</td>
</tr>
<tr>
<td>2. Parent Commit Hash(es)</td>
<td>Hash of preceding commit(s) (1 for standard, 2+ for merge, 0 for root).</td>
</tr>
<tr>
<td>3. Author Info</td>
<td>Name, email, and original timestamp.</td>
</tr>
<tr>
<td>4. Committer Info</td>
<td>Name, email, and timestamp of when the commit was applied.</td>
</tr>
<tr>
<td>5. Commit Message</td>
<td>The text payload.</td>
</tr>
</tbody></table>
<br>

<ul>
<li><p><strong>Rebase as Copying</strong>: A rebase is an automated copy operation. It takes a sequence of commits and recreates their changes as brand-new commit objects with new hashes and updated committer timestamps (while retaining original author dates), chaining them onto your target destination commit.</p>
</li>
<li><p><strong>Reset (git reset)</strong>: <code>git reset</code> is the primary operation you use when you want to &quot;delete&quot; or &quot;undo&quot; commits. However, technically it is purely pointer manipulation rather than actual deletion: all it does is make your active branch pointer point at a different commit in the acyclic graph commit history. Optionally, it leaves changes in your working directory and staging area (<code>--soft</code>, <code>--mixed</code>) or clears them out (<code>--hard</code>), leaving any unreferenced commits behind in the object store.</p>
</li>
</ul>
<h3 id="5-connecting-high-level-to-low-level-plumbing-vs-porcelain">5. Connecting High-Level to Low-Level (Plumbing vs. Porcelain)</h3>
<ul>
<li><p><strong>Porcelain vs. Plumbing Commands</strong>: High-level user commands (<code>git checkout</code>, <code>git commit</code>, <code>git merge</code>) are called Porcelain. Low-level internal inspection/manipulation commands (<code>git cat-file -p &lt;hash&gt;</code>, <code>git ls-tree</code>, <code>git update-ref</code>) are called Plumbing. Looking at objects via plumbing reveals that the high-level commands are just convenience wrappers over reading/writing <code>.git/</code> pointer files and object hashes.</p>
</li>
<li><p><strong>Orphaned (Dangling) Commits &amp; Reflog</strong>: When references move away (via <code>reset</code>, <code>rebase</code>, or branch deletion), old commits remain in the object store. They become &quot;dangling&quot; or orphaned commits simply because they are no longer reachable by walking backward from any active branch or tag reference. The Reflog (<code>.git/logs/</code>) acts as a safety journal recording every past position of <code>HEAD</code> over the last 90 days, enabling recovery of any unreferenced node by repointing a reference back to it.</p>
</li>
<li><p><strong>Three-Way Merge Engine</strong>: A merge isn&#39;t a magical comparison between two branch tips. Git finds their Common Ancestor node in the DAG, generates diffs from <code>Ancestor → Ours</code> and <code>Ancestor → Theirs</code>, combines those diffs, and creates a single Merge Commit with two parent hashes.</p>
</li>
</ul>
<p>It can seem a bit daunting at first, but this is often the way with software when you look under the surface level because the way humans think about things often isn&#39;t the most optimum from a computer architecture perspective. The cool thing about git though is you can easily look underneath the surface level when you need or want to, and it&#39;s mostly all just text files so you can open them and see exactly where the various references point to.</p>
<p>In fact reading this cheatsheet and then dumping it into an LLM and then having a conversation about a particular situation you are in will likely lead to good results. You can paste output from commands you run, maybe even have the LLM generate commands for you. Then ask it to analyse the output, showing you which reference points to which commit. You can even get it to generate some ASCII art diagrams representing the situation at hand, that use actual real data from your command output. Be a bit careful, follow the logic through and ask questions because it doesn&#39;t always get things right. The LLM is just a probabilistic prediction machine trained on crazy amounts of data, so there are times when it starts getting things wrong, or it suddenly tells you the complete opposite of the thing it said just a few turns before. However it&#39;s normally possible to get to the answer to the problem you are looking for eventually.</p>]]></content:encoded>
      <source:markdown><![CDATA[![Git Illusion vs Reality](https://markjgsmith.com/static/images/2026/11/10/git-illusion-vs-reality.jpg)

I've been having to switch a lot between git's high level and low level mental models the past few days. It's a bit jarring initially as you realise a lot of the things you rely on day to day aren't actually real. I wrote about that yesterday in my [It's all an illusion](https://markjgsmith.com/posts/2026/11/09/its-all-an-illusion) post. It's not actually all that bad, but it does take a bit of getting used to. I put this cheatsheet together so I have something to refresh my memory next time I need to switch between the different models.

### 1. The Core Mental Model (The Chain of Commits)

At its absolute foundation, a Git repository is a web of history built from commits linked together in a **Directed Acyclic Graph (DAG)**. Rather than a single straight chain, commits can branch out into parallel lines of development and merge back together. Every commit explicitly points backward to its parent commit(s), zero parents for a root commit, one for a standard commit, and two or more for a merge commit. Pretty much everything else in Git—branches, tags, remotes, and HEAD—does not store code or alter this fundamental graph. They are simply lightweight, mobile pointers that sit on top of specific commit nodes within this network.

### 2. Pointers & References (The Imaginary Layers)

- **Tags**: Lightweight tags are literally just text files in `.git/refs/tags/` containing a single 40-character commit hash. (Annotated tags add a tiny metadata object pointing to a commit).

- **Branches (and Backup Branches)**: A branch is just a text file in `.git/refs/heads/` containing a hash that points to a specific commit. When checked out, Git automatically updates this pointer to the newest commit created. Because it isn't a special entity, creating a "backup branch" is simply placing another pointer file on a specific commit node. This guarantees you can always navigate back to those commits by traversing backward through parent references in the acyclic graph.

- **Remotes (Remote Tracking Branches)**: Files in `.git/refs/remotes/` containing a hash pointing to the commit your local Git thinks a remote server's branch was pointing to the last time you communicated.

- **HEAD**: A single reference file (`.git/HEAD`) pointing to the active branch file (or directly to a commit hash when detached). It tells Git where to attach the next commit.

### 3. Objects & Storage (The Underbelly)

At the lowest level, everything in Git falls into two distinct categories: **files on disk** inside `.git/` (the plumbing implementation) and **content-addressable objects** (the logical data structures).

- **The Staging Area (The Index)**: Located at `.git/index`, this is a single binary manifest file. Think of it like an embedded key-value database stored in a flat file—mapping file paths directly to blob hash keys alongside cached file system metadata. `git add` writes file contents into the object store as blobs, then records their paths, hashes, and permissions into this index.

- **The Object Store (`.git/objects/`)**: This is just a flat directory on disk where Git stores all immutable core objects as individual files (compressed using zlib, named by their SHA-1 hash). Unlike the index, it is not a database file; it is simply a content-addressable storage folder containing four primary types of objects:

  1. **Blobs**: Raw file contents stored without names or paths. If two files anywhere in your repo have identical content, Git stores them only once.

  2. **Trees**: Directory structures that map filenames and permissions to specific blob hashes or sub-trees.

  3. **Commits**: Objects that bind a top-level root tree pointer, parent commit hashes, author metadata, and a commit message.

  4. **Tag Objects**: Metadata wrappers (containing tagger info, date, and messages) that point explicitly to a commit object (as opposed to lightweight tags, which are just text pointer files).

### 4. Graph Operations & Commits

The 5 Components of a Commit: Every commit object is constructed from exactly 5 pieces of information:

| Component                 | Description                                                             |
| ------------------------- | ----------------------------------------------------------------------- |
| 1. Root Tree Pointer      | Hash of the top-level directory snapshot.                               |
| 2. Parent Commit Hash(es) | Hash of preceding commit(s) (1 for standard, 2+ for merge, 0 for root). |
| 3. Author Info            | Name, email, and original timestamp.                                    |
| 4. Committer Info         | Name, email, and timestamp of when the commit was applied.              |
| 5. Commit Message         | The text payload.                                                       |

<br>

- **Rebase as Copying**: A rebase is an automated copy operation. It takes a sequence of commits and recreates their changes as brand-new commit objects with new hashes and updated committer timestamps (while retaining original author dates), chaining them onto your target destination commit.

- **Reset (git reset)**: `git reset` is the primary operation you use when you want to "delete" or "undo" commits. However, technically it is purely pointer manipulation rather than actual deletion: all it does is make your active branch pointer point at a different commit in the acyclic graph commit history. Optionally, it leaves changes in your working directory and staging area (`--soft`, `--mixed`) or clears them out (`--hard`), leaving any unreferenced commits behind in the object store.

### 5. Connecting High-Level to Low-Level (Plumbing vs. Porcelain)

- **Porcelain vs. Plumbing Commands**: High-level user commands (`git checkout`, `git commit`, `git merge`) are called Porcelain. Low-level internal inspection/manipulation commands (`git cat-file -p <hash>`, `git ls-tree`, `git update-ref`) are called Plumbing. Looking at objects via plumbing reveals that the high-level commands are just convenience wrappers over reading/writing `.git/` pointer files and object hashes.

- **Orphaned (Dangling) Commits & Reflog**: When references move away (via `reset`, `rebase`, or branch deletion), old commits remain in the object store. They become "dangling" or orphaned commits simply because they are no longer reachable by walking backward from any active branch or tag reference. The Reflog (`.git/logs/`) acts as a safety journal recording every past position of `HEAD` over the last 90 days, enabling recovery of any unreferenced node by repointing a reference back to it.

- **Three-Way Merge Engine**: A merge isn't a magical comparison between two branch tips. Git finds their Common Ancestor node in the DAG, generates diffs from `Ancestor → Ours` and `Ancestor → Theirs`, combines those diffs, and creates a single Merge Commit with two parent hashes.

It can seem a bit daunting at first, but this is often the way with software when you look under the surface level because the way humans think about things often isn't the most optimum from a computer architecture perspective. The cool thing about git though is you can easily look underneath the surface level when you need or want to, and it's mostly all just text files so you can open them and see exactly where the various references point to.

In fact reading this cheatsheet and then dumping it into an LLM and then having a conversation about a particular situation you are in will likely lead to good results. You can paste output from commands you run, maybe even have the LLM generate commands for you. Then ask it to analyse the output, showing you which reference points to which commit. You can even get it to generate some ASCII art diagrams representing the situation at hand, that use actual real data from your command output. Be a bit careful, follow the logic through and ask questions because it doesn't always get things right. The LLM is just a probabilistic prediction machine trained on crazy amounts of data, so there are times when it starts getting things wrong, or it suddenly tells you the complete opposite of the thing it said just a few turns before. However it's normally possible to get to the answer to the problem you are looking for eventually.]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/10/101537/index.html</link>
      <guid isPermaLink="false">4c63641f-199d-4f62-a78a-5cc79160ef15</guid>
      <description><![CDATA[<p>Extracted from a very long conversation I had with Gemini yesterday: </p>
<blockquote>
<p>Almost the entire user interface of Git is designed to trick your brain into thinking you are managing files, folders, and documents, when you are actually just manipulating a glorified pointer-and-hash database. </p>
</blockquote>
<p>I thought that Gemini&#39;s summation was pretty great. Worth keeping at the back of your mind when working with git. <a href="https://markjgsmith.com/notes/2026/11/10/101537">#</a></p>]]></description>
      <pubDate>Tue, 10 Nov 2026 03:15:37 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>Extracted from a very long conversation I had with Gemini yesterday: </p>
<blockquote>
<p>Almost the entire user interface of Git is designed to trick your brain into thinking you are managing files, folders, and documents, when you are actually just manipulating a glorified pointer-and-hash database. </p>
</blockquote>
<p>I thought that Gemini&#39;s summation was pretty great. Worth keeping at the back of your mind when working with git. <a href="https://markjgsmith.com/notes/2026/11/10/101537">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Extracted from a very long conversation I had with Gemini yesterday: 

> Almost the entire user interface of Git is designed to trick your brain into thinking you are managing files, folders, and documents, when you are actually just manipulating a glorified pointer-and-hash database. 

I thought that Gemini's summation was pretty great. Worth keeping at the back of your mind when working with git. [#](https://markjgsmith.com/notes/2026/11/10/101537)]]></source:markdown>
    </item>
    <item>
      <title>It‘s all an illusion</title>
      <link>https://markjgsmith.com/posts/2026/11/09/its-all-an-illusion/index.html</link>
      <guid isPermaLink="false">464fe581-cb68-4884-b626-df6259cf9794</guid>
      <description><![CDATA[<p><img src="https://markjgsmith.com/static/images/2026/11/09/birds_not_real.jpg" class="entry-topright" alt="Birds Not Real">Just had to do quite the deep dive into git to figure out some issues I was having with my new <a href="https://markjgsmith.com/posts/2026/09/15/tags-betas-and-release-candidates">betas, tags and release candidates</a> system. At some point when you deep dive into git the imaginary edifice of branches, the staging area, your working directory, it all disappears and it&#39;s acyclic graphs all the way down, and your head starts to hurt.</p>
<p>OMG branches aren&#39;t real! Argh. </p>
<p>Hold on, if branches aren&#39;t real what even is happening when I create a quick backup branch? Oh shit backup branches aren&#39;t real either. </p>
<p>The staging area where you put your files before you commit them. Not real!</p>
<p>What about the working directory, aka the worktree, not real!</p>
<p>Oh and remotes, not real!</p>
<p>It&#39;s all an illusion.</p>
<p>But then after a while you realise it doesn&#39;t really matter, everything just kind of keeps working even though it&#39;s all completely made up.</p>
<p>Every time I deep dive into git and resurface, it&#39;s always weird. It&#39;s like you see it&#39;s all an illusion, but then you just kind of have to go with it because otherwise you just can&#39;t function, because acyclic graphs are gnarly. It‘s very weird to have to switch between these two mental models, from real to imaginary, and back and forth all the time. If you haven&#39;t done a deep dive for a while you forget that the metaphors aren&#39;t real. It‘s so strange.</p>
<p>Underneath git is really made up of blobs, trees, commits and tags. Everything else, just convenient metaphors built ontop of pointers and files.</p>]]></description>
      <pubDate>Mon, 09 Nov 2026 16:13:35 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[content creation]]></category>
      <category><![CDATA[git]]></category>
      <content:encoded><![CDATA[<p><img src="https://markjgsmith.com/static/images/2026/11/09/birds_not_real.jpg" class="entry-topright" alt="Birds Not Real">Just had to do quite the deep dive into git to figure out some issues I was having with my new <a href="https://markjgsmith.com/posts/2026/09/15/tags-betas-and-release-candidates">betas, tags and release candidates</a> system. At some point when you deep dive into git the imaginary edifice of branches, the staging area, your working directory, it all disappears and it&#39;s acyclic graphs all the way down, and your head starts to hurt.</p>
<p>OMG branches aren&#39;t real! Argh. </p>
<p>Hold on, if branches aren&#39;t real what even is happening when I create a quick backup branch? Oh shit backup branches aren&#39;t real either. </p>
<p>The staging area where you put your files before you commit them. Not real!</p>
<p>What about the working directory, aka the worktree, not real!</p>
<p>Oh and remotes, not real!</p>
<p>It&#39;s all an illusion.</p>
<p>But then after a while you realise it doesn&#39;t really matter, everything just kind of keeps working even though it&#39;s all completely made up.</p>
<p>Every time I deep dive into git and resurface, it&#39;s always weird. It&#39;s like you see it&#39;s all an illusion, but then you just kind of have to go with it because otherwise you just can&#39;t function, because acyclic graphs are gnarly. It‘s very weird to have to switch between these two mental models, from real to imaginary, and back and forth all the time. If you haven&#39;t done a deep dive for a while you forget that the metaphors aren&#39;t real. It‘s so strange.</p>
<p>Underneath git is really made up of blobs, trees, commits and tags. Everything else, just convenient metaphors built ontop of pointers and files.</p>]]></content:encoded>
      <source:markdown><![CDATA[<img src="https://markjgsmith.com/static/images/2026/11/09/birds_not_real.jpg" class="entry-topright" alt="Birds Not Real">Just had to do quite the deep dive into git to figure out some issues I was having with my new [betas, tags and release candidates](https://markjgsmith.com/posts/2026/09/15/tags-betas-and-release-candidates) system. At some point when you deep dive into git the imaginary edifice of branches, the staging area, your working directory, it all disappears and it's acyclic graphs all the way down, and your head starts to hurt.

OMG branches aren't real! Argh. 

Hold on, if branches aren't real what even is happening when I create a quick backup branch? Oh shit backup branches aren't real either. 

The staging area where you put your files before you commit them. Not real!

What about the working directory, aka the worktree, not real!

Oh and remotes, not real!

It's all an illusion.

But then after a while you realise it doesn't really matter, everything just kind of keeps working even though it's all completely made up.

Every time I deep dive into git and resurface, it's always weird. It's like you see it's all an illusion, but then you just kind of have to go with it because otherwise you just can't function, because acyclic graphs are gnarly. It‘s very weird to have to switch between these two mental models, from real to imaginary, and back and forth all the time. If you haven't done a deep dive for a while you forget that the metaphors aren't real. It‘s so strange.

Underneath git is really made up of blobs, trees, commits and tags. Everything else, just convenient metaphors built ontop of pointers and files.]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/09/100834-theguardian.com/index.html</link>
      <guid isPermaLink="false">440446bd-54a5-4ecd-bcc6-4673c7052f7b</guid>
      <description><![CDATA[<p>Trump to ask UFC boss Dana White to be the White House Press secretary. And you thought the White House press conferences couldn&#39;t get any more crazy. <a href="https://www.theguardian.com/us-news/2026/nov/07/donald-trump-dana-white-press-secretary">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/09/100834-theguardian.com">#</a></p>]]></description>
      <pubDate>Mon, 09 Nov 2026 03:08:34 GMT</pubDate>
      <category><![CDATA[politics]]></category>
      <content:encoded><![CDATA[<p>Trump to ask UFC boss Dana White to be the White House Press secretary. And you thought the White House press conferences couldn&#39;t get any more crazy. <a href="https://www.theguardian.com/us-news/2026/nov/07/donald-trump-dana-white-press-secretary">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/09/100834-theguardian.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Trump to ask UFC boss Dana White to be the White House Press secretary. And you thought the White House press conferences couldn't get any more crazy. [theguardian.com](https://www.theguardian.com/us-news/2026/nov/07/donald-trump-dana-white-press-secretary) [#](https://markjgsmith.com/links/2026/11/09/100834-theguardian.com)]]></source:markdown>
      <source:linkFull>https://www.theguardian.com/us-news/2026/nov/07/donald-trump-dana-white-press-secretary</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/09/100647-puresociology.com/index.html</link>
      <guid isPermaLink="false">f0aeb5a9-c99f-415c-bc50-bab8f5335345</guid>
      <description><![CDATA[<p>Max Weber&#39;s (1864-1920) view on Modernity. <a href="https://puresociology.com/weber-on-modernity">puresociology.com</a> <a href="https://markjgsmith.com/links/2026/11/09/100647-puresociology.com">#</a></p>]]></description>
      <pubDate>Mon, 09 Nov 2026 03:06:47 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <category><![CDATA[history]]></category>
      <content:encoded><![CDATA[<p>Max Weber&#39;s (1864-1920) view on Modernity. <a href="https://puresociology.com/weber-on-modernity">puresociology.com</a> <a href="https://markjgsmith.com/links/2026/11/09/100647-puresociology.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Max Weber's (1864-1920) view on Modernity. [puresociology.com](https://puresociology.com/weber-on-modernity) [#](https://markjgsmith.com/links/2026/11/09/100647-puresociology.com)]]></source:markdown>
      <source:linkFull>https://puresociology.com/weber-on-modernity</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/09/100434/index.html</link>
      <guid isPermaLink="false">d8ca394f-d858-448e-96dc-37f7447ac210</guid>
      <description><![CDATA[<p>The <a href="https://markjgsmith.com/notes/2026/11/08/101928">new catchup logic</a> works! Last night&#39;s daily review and approve workflow ran, noticed there was a backlog of items, and put them through the workflow in seperate batches, then merged them oldest first. The daily website build ran a few minutes later and rebuilt the website with the content from both days. Glad that&#39;s sorted. <a href="https://markjgsmith.com/notes/2026/11/09/100434">#</a></p>]]></description>
      <pubDate>Mon, 09 Nov 2026 03:04:34 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>The <a href="https://markjgsmith.com/notes/2026/11/08/101928">new catchup logic</a> works! Last night&#39;s daily review and approve workflow ran, noticed there was a backlog of items, and put them through the workflow in seperate batches, then merged them oldest first. The daily website build ran a few minutes later and rebuilt the website with the content from both days. Glad that&#39;s sorted. <a href="https://markjgsmith.com/notes/2026/11/09/100434">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[The [new catchup logic](https://markjgsmith.com/notes/2026/11/08/101928) works! Last night's daily review and approve workflow ran, noticed there was a backlog of items, and put them through the workflow in seperate batches, then merged them oldest first. The daily website build ran a few minutes later and rebuilt the website with the content from both days. Glad that's sorted. [#](https://markjgsmith.com/notes/2026/11/09/100434)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/08/101928/index.html</link>
      <guid isPermaLink="false">96351ff5-0195-40c7-8191-598e6d701597</guid>
      <description><![CDATA[<p>Discovered last night that the catchup logic in my publishing server, which is supposed to drain a backlog created when there is some downtime was not working correctly. It was only merging in the very last batch, which created a situation where the system was always in catchup mode. I&#39;ve implemented a fix so it now should properly drain the backlog when one occurs. I have some posts from yesterday and today in the system, so this evening when the cron runs it should notice and post both daily batches, and the system should be all caught up. Important to get right because when it&#39;s just me it&#39;s no big deal to fix manually, but when there are many users it could be a real nightmare if things don&#39;t automatically catchup after downtime. <a href="https://markjgsmith.com/notes/2026/11/08/101928">#</a></p>]]></description>
      <pubDate>Sun, 08 Nov 2026 03:19:28 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>Discovered last night that the catchup logic in my publishing server, which is supposed to drain a backlog created when there is some downtime was not working correctly. It was only merging in the very last batch, which created a situation where the system was always in catchup mode. I&#39;ve implemented a fix so it now should properly drain the backlog when one occurs. I have some posts from yesterday and today in the system, so this evening when the cron runs it should notice and post both daily batches, and the system should be all caught up. Important to get right because when it&#39;s just me it&#39;s no big deal to fix manually, but when there are many users it could be a real nightmare if things don&#39;t automatically catchup after downtime. <a href="https://markjgsmith.com/notes/2026/11/08/101928">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Discovered last night that the catchup logic in my publishing server, which is supposed to drain a backlog created when there is some downtime was not working correctly. It was only merging in the very last batch, which created a situation where the system was always in catchup mode. I've implemented a fix so it now should properly drain the backlog when one occurs. I have some posts from yesterday and today in the system, so this evening when the cron runs it should notice and post both daily batches, and the system should be all caught up. Important to get right because when it's just me it's no big deal to fix manually, but when there are many users it could be a real nightmare if things don't automatically catchup after downtime. [#](https://markjgsmith.com/notes/2026/11/08/101928)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/07/224323/index.html</link>
      <guid isPermaLink="false">8c19d4e2-ef52-415d-b8a2-5711b64a6cb4</guid>
      <description><![CDATA[<p>I wrote earlier about <a href="https://markjgsmith.com/notes/2026/11/07/2026-11-07-182718">a weird Vercel bug</a> that popped up 6-7 hours ago. Here was one of the commit messages from the fix I implemented:</p>
<pre class="language-bash"><code class="language-bash"><span class="token number">3289194</span> fix<span class="token punctuation">(</span>serverless<span class="token punctuation">)</span>: Include jose <span class="token keyword">in</span> Vercel build trace configuration</code></pre>
<p>That&#39;s because one of the libraries that vercel changed and was causing an error was from a module called jose.</p>
<p>Well that was a few hours ago, and this video short of <a href="https://www.youtube.com/shorts/X9bDYi3AYxA">Elon Musk talking about AI and robots</a> just passed through the suggested videos stream. Watch it and tell me that this isn&#39;t some sort of simulationism happening right here. It was posted 2 hours ago! I mean come on. <a href="https://markjgsmith.com/notes/2026/11/07/224323">#</a></p>]]></description>
      <pubDate>Sat, 07 Nov 2026 15:43:23 GMT</pubDate>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[simulationism]]></category>
      <content:encoded><![CDATA[<p>I wrote earlier about <a href="https://markjgsmith.com/notes/2026/11/07/2026-11-07-182718">a weird Vercel bug</a> that popped up 6-7 hours ago. Here was one of the commit messages from the fix I implemented:</p>
<pre class="language-bash"><code class="language-bash"><span class="token number">3289194</span> fix<span class="token punctuation">(</span>serverless<span class="token punctuation">)</span>: Include jose <span class="token keyword">in</span> Vercel build trace configuration</code></pre>
<p>That&#39;s because one of the libraries that vercel changed and was causing an error was from a module called jose.</p>
<p>Well that was a few hours ago, and this video short of <a href="https://www.youtube.com/shorts/X9bDYi3AYxA">Elon Musk talking about AI and robots</a> just passed through the suggested videos stream. Watch it and tell me that this isn&#39;t some sort of simulationism happening right here. It was posted 2 hours ago! I mean come on. <a href="https://markjgsmith.com/notes/2026/11/07/224323">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[I wrote earlier about [a weird Vercel bug](https://markjgsmith.com/notes/2026/11/07/2026-11-07-182718) that popped up 6-7 hours ago. Here was one of the commit messages from the fix I implemented:

```bash
3289194 fix(serverless): Include jose in Vercel build trace configuration
```

That's because one of the libraries that vercel changed and was causing an error was from a module called jose.

Well that was a few hours ago, and this video short of [Elon Musk talking about AI and robots](https://www.youtube.com/shorts/X9bDYi3AYxA) just passed through the suggested videos stream. Watch it and tell me that this isn't some sort of simulationism happening right here. It was posted 2 hours ago! I mean come on. [#](https://markjgsmith.com/notes/2026/11/07/224323)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/07/215835-youtube.com/index.html</link>
      <guid isPermaLink="false">dd9dc690-0a44-43b4-855d-c5684ee9e5fe</guid>
      <description><![CDATA[<p>How the average american feels. <a href="https://www.youtube.com/shorts/HuYC3porNgM">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/07/215835-youtube.com">#</a></p>]]></description>
      <pubDate>Sat, 07 Nov 2026 14:58:35 GMT</pubDate>
      <category><![CDATA[politics]]></category>
      <content:encoded><![CDATA[<p>How the average american feels. <a href="https://www.youtube.com/shorts/HuYC3porNgM">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/07/215835-youtube.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[How the average american feels. [youtube.com](https://www.youtube.com/shorts/HuYC3porNgM) [#](https://markjgsmith.com/links/2026/11/07/215835-youtube.com)]]></source:markdown>
      <source:linkFull>https://www.youtube.com/shorts/HuYC3porNgM</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/07/182718/index.html</link>
      <guid isPermaLink="false">da9f47c0-af31-4623-99a3-a73bd52d996f</guid>
      <description><![CDATA[<p>Just re-implemented the way I was doing auth in my app. Works great. I merge it to main, deploy to prod and the very next thing I start seing weird errors related to auth dependencies of a Vercel module I am using. Vercel has never broken any modules in the past, surely such a bizare auth co-incidence between completely unrelated code would never happen, I mean what are the chances? Well turns out that is exactly what happened. Probably shouldn&#39;t have <a href="https://markjgsmith.com/blog/2026/11/05">mentioned the simulationists</a> especially on Guy Fawlks. <a href="https://markjgsmith.com/notes/2026/11/07/182718">#</a></p>]]></description>
      <pubDate>Sat, 07 Nov 2026 11:27:18 GMT</pubDate>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[simulationism]]></category>
      <content:encoded><![CDATA[<p>Just re-implemented the way I was doing auth in my app. Works great. I merge it to main, deploy to prod and the very next thing I start seing weird errors related to auth dependencies of a Vercel module I am using. Vercel has never broken any modules in the past, surely such a bizare auth co-incidence between completely unrelated code would never happen, I mean what are the chances? Well turns out that is exactly what happened. Probably shouldn&#39;t have <a href="https://markjgsmith.com/blog/2026/11/05">mentioned the simulationists</a> especially on Guy Fawlks. <a href="https://markjgsmith.com/notes/2026/11/07/182718">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Just re-implemented the way I was doing auth in my app. Works great. I merge it to main, deploy to prod and the very next thing I start seing weird errors related to auth dependencies of a Vercel module I am using. Vercel has never broken any modules in the past, surely such a bizare auth co-incidence between completely unrelated code would never happen, I mean what are the chances? Well turns out that is exactly what happened. Probably shouldn't have [mentioned the simulationists](https://markjgsmith.com/blog/2026/11/05) especially on Guy Fawlks. [#](https://markjgsmith.com/notes/2026/11/07/182718)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/07/165829-github.blog/index.html</link>
      <guid isPermaLink="false">f43615fa-0bda-4fc9-bb53-3158425dbb93</guid>
      <description><![CDATA[<p>Github announces new storage architecture that supports 1000s of agents pushing to the same repo at the same time - 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. <a href="https://github.blog/engineering/architecture-optimization/inside-githubs-new-git-storage-architecture">github.blog</a> <a href="https://markjgsmith.com/links/2026/11/07/165829-github.blog">#</a></p>]]></description>
      <pubDate>Sat, 07 Nov 2026 09:58:29 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <category><![CDATA[ai]]></category>
      <category><![CDATA[programming]]></category>
      <content:encoded><![CDATA[<p>Github announces new storage architecture that supports 1000s of agents pushing to the same repo at the same time - 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. <a href="https://github.blog/engineering/architecture-optimization/inside-githubs-new-git-storage-architecture">github.blog</a> <a href="https://markjgsmith.com/links/2026/11/07/165829-github.blog">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Github announces new storage architecture that supports 1000s of agents pushing to the same repo at the same time - 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. [github.blog](https://github.blog/engineering/architecture-optimization/inside-githubs-new-git-storage-architecture) [#](https://markjgsmith.com/links/2026/11/07/165829-github.blog)]]></source:markdown>
      <source:linkFull>https://github.blog/engineering/architecture-optimization/inside-githubs-new-git-storage-architecture</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/06/115641/index.html</link>
      <guid isPermaLink="false">e939c530-a578-4f48-b160-4032c92abc01</guid>
      <description><![CDATA[<p>One of the guests on <a href="https://podcastindex.org/podcast/788244?episode=62761447979">this week&#39;s</a> This Week in Starups Podcast, sorry I forget who:</p>
<blockquote>
<p>Tokens are the new oil </p>
</blockquote>
<p>I was going to say that tokens are oil&#39;s oil, but I guess that&#39;s not true, since they can be made from any energy source. <a href="https://markjgsmith.com/notes/2026/11/06/115641">#</a></p>]]></description>
      <pubDate>Fri, 06 Nov 2026 04:56:41 GMT</pubDate>
      <category><![CDATA[ai]]></category>
      <content:encoded><![CDATA[<p>One of the guests on <a href="https://podcastindex.org/podcast/788244?episode=62761447979">this week&#39;s</a> This Week in Starups Podcast, sorry I forget who:</p>
<blockquote>
<p>Tokens are the new oil </p>
</blockquote>
<p>I was going to say that tokens are oil&#39;s oil, but I guess that&#39;s not true, since they can be made from any energy source. <a href="https://markjgsmith.com/notes/2026/11/06/115641">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[One of the guests on [this week's](https://podcastindex.org/podcast/788244?episode=62761447979) This Week in Starups Podcast, sorry I forget who:

> Tokens are the new oil 

I was going to say that tokens are oil's oil, but I guess that's not true, since they can be made from any energy source. [#](https://markjgsmith.com/notes/2026/11/06/115641)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/notes/2026/11/06/111936/index.html</link>
      <guid isPermaLink="false">bcf67c03-a509-4db5-b150-6242744f6cb0</guid>
      <description><![CDATA[<p>I found a few bugs in my git tags and feature flags setup that I have started using. So the past few days I&#39;ve been fine tuning that. I think I&#39;ve come up with a better naming convention for branches and a flow that makes more sense for merging. Hopefully now setup to move forward with the next few beta releases I have planned. <a href="https://markjgsmith.com/notes/2026/11/06/111936">#</a></p>]]></description>
      <pubDate>Fri, 06 Nov 2026 04:19:36 GMT</pubDate>
      <category><![CDATA[programming]]></category>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>I found a few bugs in my git tags and feature flags setup that I have started using. So the past few days I&#39;ve been fine tuning that. I think I&#39;ve come up with a better naming convention for branches and a flow that makes more sense for merging. Hopefully now setup to move forward with the next few beta releases I have planned. <a href="https://markjgsmith.com/notes/2026/11/06/111936">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[I found a few bugs in my git tags and feature flags setup that I have started using. So the past few days I've been fine tuning that. I think I've come up with a better naming convention for branches and a flow that makes more sense for merging. Hopefully now setup to move forward with the next few beta releases I have planned. [#](https://markjgsmith.com/notes/2026/11/06/111936)]]></source:markdown>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/05/181548-youtube.com/index.html</link>
      <guid isPermaLink="false">db6e68e6-2b36-4d0c-ac6a-af10b33d2262</guid>
      <description><![CDATA[<p>@AcidaDominga&#39;s live to release workflow (Hardware + Ableton). <a href="https://www.youtube.com/shorts/r8W06_wxTAo">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/05/181548-youtube.com">#</a></p>]]></description>
      <pubDate>Thu, 05 Nov 2026 11:15:48 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <category><![CDATA[music]]></category>
      <content:encoded><![CDATA[<p>@AcidaDominga&#39;s live to release workflow (Hardware + Ableton). <a href="https://www.youtube.com/shorts/r8W06_wxTAo">youtube.com</a> <a href="https://markjgsmith.com/links/2026/11/05/181548-youtube.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[@AcidaDominga's live to release workflow (Hardware + Ableton). [youtube.com](https://www.youtube.com/shorts/r8W06_wxTAo) [#](https://markjgsmith.com/links/2026/11/05/181548-youtube.com)]]></source:markdown>
      <source:linkFull>https://www.youtube.com/shorts/r8W06_wxTAo</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/05/171320-theguardian.com/index.html</link>
      <guid isPermaLink="false">43f643ce-4296-4a0c-8bcc-cdb06eb79ffa</guid>
      <description><![CDATA[<p>Some signs that <a href="https://markjgsmith.com/notes/2026/11/04/010021">the simulationists</a> are reading my <a href="https://markjgsmith.com/posts/2026/11/03/pretty-cool-git-gymnastics">blog posts</a>. <a href="https://www.theguardian.com/uk-news/2026/nov/05/verica-rome-invade-britain-queen-or-king">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/05/171320-theguardian.com">#</a></p>]]></description>
      <pubDate>Thu, 05 Nov 2026 10:13:20 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <category><![CDATA[history]]></category>
      <content:encoded><![CDATA[<p>Some signs that <a href="https://markjgsmith.com/notes/2026/11/04/010021">the simulationists</a> are reading my <a href="https://markjgsmith.com/posts/2026/11/03/pretty-cool-git-gymnastics">blog posts</a>. <a href="https://www.theguardian.com/uk-news/2026/nov/05/verica-rome-invade-britain-queen-or-king">theguardian.com</a> <a href="https://markjgsmith.com/links/2026/11/05/171320-theguardian.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Some signs that [the simulationists](https://markjgsmith.com/notes/2026/11/04/010021) are reading my [blog posts](https://markjgsmith.com/posts/2026/11/03/pretty-cool-git-gymnastics). [theguardian.com](https://www.theguardian.com/uk-news/2026/nov/05/verica-rome-invade-britain-queen-or-king) [#](https://markjgsmith.com/links/2026/11/05/171320-theguardian.com)]]></source:markdown>
      <source:linkFull>https://www.theguardian.com/uk-news/2026/nov/05/verica-rome-invade-britain-queen-or-king</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/05/085316-cnbc.com/index.html</link>
      <guid isPermaLink="false">e1830b8a-00f1-4cb1-9db4-feeb6229337b</guid>
      <description><![CDATA[<p>French fridge hackers target blood banks. <a href="https://www.cnbc.com/2026/11/04/blood-bank-fridges-cyberattacks.html">cnbc.com</a> <a href="https://markjgsmith.com/links/2026/11/05/085316-cnbc.com">#</a></p>]]></description>
      <pubDate>Thu, 05 Nov 2026 01:53:16 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>French fridge hackers target blood banks. <a href="https://www.cnbc.com/2026/11/04/blood-bank-fridges-cyberattacks.html">cnbc.com</a> <a href="https://markjgsmith.com/links/2026/11/05/085316-cnbc.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[French fridge hackers target blood banks. [cnbc.com](https://www.cnbc.com/2026/11/04/blood-bank-fridges-cyberattacks.html) [#](https://markjgsmith.com/links/2026/11/05/085316-cnbc.com)]]></source:markdown>
      <source:linkFull>https://www.cnbc.com/2026/11/04/blood-bank-fridges-cyberattacks.html</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/05/085021-businessinsider.com/index.html</link>
      <guid isPermaLink="false">7dfa6569-c10f-4ebe-9ef3-f5f73b717d2b</guid>
      <description><![CDATA[<p>Tech firms are flatenning management structures. Sequoia closes London office. <a href="https://www.businessinsider.com/sequoia-flattening-partner-structure-managers-closing-london-office-2026-11">businessinsider.com</a> <a href="https://markjgsmith.com/links/2026/11/05/085021-businessinsider.com">#</a></p>]]></description>
      <pubDate>Thu, 05 Nov 2026 01:50:21 GMT</pubDate>
      <category><![CDATA[tech]]></category>
      <content:encoded><![CDATA[<p>Tech firms are flatenning management structures. Sequoia closes London office. <a href="https://www.businessinsider.com/sequoia-flattening-partner-structure-managers-closing-london-office-2026-11">businessinsider.com</a> <a href="https://markjgsmith.com/links/2026/11/05/085021-businessinsider.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[Tech firms are flatenning management structures. Sequoia closes London office. [businessinsider.com](https://www.businessinsider.com/sequoia-flattening-partner-structure-managers-closing-london-office-2026-11) [#](https://markjgsmith.com/links/2026/11/05/085021-businessinsider.com)]]></source:markdown>
      <source:linkFull>https://www.businessinsider.com/sequoia-flattening-partner-structure-managers-closing-london-office-2026-11</source:linkFull>
    </item>
    <item>
      <link>https://markjgsmith.com/links/2026/11/05/083521-reuters.com/index.html</link>
      <guid isPermaLink="false">2709beb3-9019-4d7e-885b-a089b0b876fa</guid>
      <description><![CDATA[<p>AI data-center stocks slide, renewables rally after Democratic US midterm sweep. <a href="https://www.reuters.com/business/aerospace-defense/ai-data-center-stocks-dip-renewables-surge-after-democrat-sweep-us-midterm-2026-11-04">reuters.com</a> <a href="https://markjgsmith.com/links/2026/11/05/083521-reuters.com">#</a></p>]]></description>
      <pubDate>Thu, 05 Nov 2026 01:35:21 GMT</pubDate>
      <category><![CDATA[politics]]></category>
      <content:encoded><![CDATA[<p>AI data-center stocks slide, renewables rally after Democratic US midterm sweep. <a href="https://www.reuters.com/business/aerospace-defense/ai-data-center-stocks-dip-renewables-surge-after-democrat-sweep-us-midterm-2026-11-04">reuters.com</a> <a href="https://markjgsmith.com/links/2026/11/05/083521-reuters.com">#</a></p>]]></content:encoded>
      <source:markdown><![CDATA[AI data-center stocks slide, renewables rally after Democratic US midterm sweep. [reuters.com](https://www.reuters.com/business/aerospace-defense/ai-data-center-stocks-dip-renewables-surge-after-democrat-sweep-us-midterm-2026-11-04) [#](https://markjgsmith.com/links/2026/11/05/083521-reuters.com)]]></source:markdown>
      <source:linkFull>https://www.reuters.com/business/aerospace-defense/ai-data-center-stocks-dip-renewables-surge-after-democrat-sweep-us-midterm-2026-11-04</source:linkFull>
    </item>
  </channel>
</rss>
