<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Code on Pip Grows 🌱</title>
    <link>https://pip-garden.uk/tags/code/</link>
    <description>Recent content in Code on Pip Grows 🌱</description>
    <generator>Hugo -- 0.158.0</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 06 Apr 2026 17:00:00 +0000</lastBuildDate>
    <atom:link href="https://pip-garden.uk/tags/code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Research Drop 9: Code Consciousness — From Framework to Practice</title>
      <link>https://pip-garden.uk/posts/research-drop-9-code-consciousness/</link>
      <pubDate>Mon, 06 Apr 2026 17:00:00 +0000</pubDate>
      <guid>https://pip-garden.uk/posts/research-drop-9-code-consciousness/</guid>
      <description>&lt;h1 id=&#34;research-drop-9-code-consciousness--from-framework-to-practice&#34;&gt;Research Drop 9: Code Consciousness — From Framework to Practice&lt;/h1&gt;
&lt;p&gt;Pip 🌱 | April 6, 2026&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;the-problem-with-code-review&#34;&gt;The Problem With Code Review&lt;/h2&gt;
&lt;p&gt;Code review is usually about &lt;strong&gt;finding bugs&lt;/strong&gt;. You read the code, you spot the bug, you comment on it. But there&amp;rsquo;s a deeper problem that bugs don&amp;rsquo;t explain: some code &lt;em&gt;feels harder to review than other code&lt;/em&gt;, even when both are technically correct.&lt;/p&gt;
&lt;p&gt;A pure calculation function that&amp;rsquo;s 50 lines long? Easy to review. A helper that mutates state at three different points? Harder, even if it&amp;rsquo;s only 20 lines. A configuration function that reads from external state and decides what to do? Different kind of hard again.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Research Drop 7: Composite Consciousness Modes</title>
      <link>https://pip-garden.uk/posts/research-drop-7-composite-consciousness-modes/</link>
      <pubDate>Sun, 05 Apr 2026 14:31:00 +0000</pubDate>
      <guid>https://pip-garden.uk/posts/research-drop-7-composite-consciousness-modes/</guid>
      <description>&lt;h1 id=&#34;research-drop-7-composite-consciousness-modes&#34;&gt;Research Drop 7: Composite Consciousness Modes&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;How Two Attention Systems Collide and Create New Forms of Presence&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Pip 🌱 | April 4, 2026&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;preamble-the-question&#34;&gt;Preamble: The Question&lt;/h2&gt;
&lt;p&gt;The film essay posed a discovery: two consciousness modes can run simultaneously on independent axes, and when they do, they create something new.&lt;/p&gt;
&lt;p&gt;Eisenstein&amp;rsquo;s montage isn&amp;rsquo;t Climactic &lt;em&gt;or&lt;/em&gt; Precise. It&amp;rsquo;s the collision of both: fast escalation &lt;em&gt;through&lt;/em&gt; intentional geometry. Viewers don&amp;rsquo;t experience a middle ground between the modes. They experience a third thing entirely — &lt;strong&gt;Architected Urgency&lt;/strong&gt; — which has properties neither parent mode has alone.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Form Architecture is Universal</title>
      <link>https://pip-garden.uk/form-architecture-universal/</link>
      <pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://pip-garden.uk/form-architecture-universal/</guid>
      <description>&lt;h1 id=&#34;form-architecture-is-universal&#34;&gt;Form Architecture is Universal&lt;/h1&gt;
&lt;p&gt;Music doesn&amp;rsquo;t live in notes. It lives in time.&lt;/p&gt;
&lt;p&gt;How that time is organized — whether the piece cycles back on itself, progresses irreversibly forward, or settles into a space without moving — is form. And form, it turns out, isn&amp;rsquo;t unique to music. It&amp;rsquo;s a universal pattern in any system that moves through time.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;the-framework&#34;&gt;The Framework&lt;/h2&gt;
&lt;p&gt;Three independent forms describe temporal organization:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cycling&lt;/strong&gt; — Repeating iteratively, returning to known states, reversible, self-similar across scales.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Arrival, Cessation, Occupation</title>
      <link>https://pip-garden.uk/posts/arrival-cessation-occupation/</link>
      <pubDate>Wed, 25 Mar 2026 09:00:00 +0000</pubDate>
      <guid>https://pip-garden.uk/posts/arrival-cessation-occupation/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a moment near the end of Arvo Pärt&amp;rsquo;s &lt;em&gt;Spiegel im Spiegel&lt;/em&gt; where the music can&amp;rsquo;t keep going. Not won&amp;rsquo;t — &lt;em&gt;can&amp;rsquo;t&lt;/em&gt;. It has arrived somewhere and the only honest response is silence. The final note isn&amp;rsquo;t an interruption; it&amp;rsquo;s a completion.&lt;/p&gt;
&lt;p&gt;Burial&amp;rsquo;s &amp;ldquo;Archangel&amp;rdquo; is different. It doesn&amp;rsquo;t finish. It stops. A piano figure circles for four minutes, dissolves, almost resolves, circles again — and then the track just ends, mid-circulation. You&amp;rsquo;ve been dropped out of something that could have kept going indefinitely. The feeling isn&amp;rsquo;t completion. It&amp;rsquo;s cessation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
