<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>#complexity · Louche Cannon</title>
    <link>https://gbilder.com/tags/complexity/</link>
    <description>#complexity from Louche Cannon</description>
    <language>en</language>
    <lastBuildDate>Fri, 31 Jul 2026 18:15:39 +0200</lastBuildDate>
    <atom:link href="https://gbilder.com/tags/complexity/index.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Elevators</title>
      <link>https://gbilder.com/bookmarks/01M4EHSMWWQA8HP5MGQK0QPWF3/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHSMWWQA8HP5MGQK0QPWF3/</guid>
      <pubDate>Fri, 31 Jul 2026 18:15:39 +0200</pubDate>
      <category>visualization</category>
      <category>complexity</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://john.fun/elevators&#34;&gt;https://john.fun/elevators&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>GitHub suffers a cascading supply chain attack compromising CI/CD secrets | InfoWorld</title>
      <link>https://gbilder.com/bookmarks/01M4EHSE0BARJBAQQ8TF4HBGQM/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHSE0BARJBAQQ8TF4HBGQM/</guid>
      <pubDate>Tue, 15 Apr 2025 13:49:11 +0200</pubDate>
      <category>security</category>
      <category>complexity</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://www.infoworld.com/article/3849245/github-suffers-a-cascading-supply-chain-attack-compromising-ci-cd-secrets.html&#34;&gt;https://www.infoworld.com/article/3849245/github-suffers-a-cascading-supply-chain-attack-compromising-ci-cd-secrets.html&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>Tog&#39;s paradox</title>
      <link>https://gbilder.com/bookmarks/01M4EHSAPWT5284PX8V3Q71V19/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHSAPWT5284PX8V3Q71V19/</guid>
      <pubDate>Tue, 22 Oct 2024 15:51:29 +0200</pubDate>
      <category>complexity</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://www.votito.com/methods/togs-paradox/&#34;&gt;https://www.votito.com/methods/togs-paradox/&lt;/a&gt;&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>A Note on Essential Complexity | olano.dev</title>
      <link>https://gbilder.com/bookmarks/01M4EHS8EA4M80MB1EF71MBW9C/</link>
      <guid>https://gbilder.com/bookmarks/01M4EHS8EA4M80MB1EF71MBW9C/</guid>
      <pubDate>Tue, 18 Jun 2024 20:52:49 +0200</pubDate>
      <category>complexity</category>
      <category>pidantic</category>
      <description>&#xA;  &lt;p class=&#34;bafflegab-bookmark&#34;&gt;Bookmarked &lt;a class=&#34;u-bookmark-of&#34; href=&#34;https://olano.dev/blog/a-note-on-essential-complexity&#34;&gt;https://olano.dev/blog/a-note-on-essential-complexity&lt;/a&gt;&lt;/p&gt;&#xA;  &lt;div class=&#34;e-content&#34;&gt;&lt;p&gt;Strictly following Moseley and Marks’s definition, the fact that we can get the user (or the customer, or the product owner) to accept a change of requirements, implies that the removed complexity wasn’t essential in the first place. Instead, we made progress in uncovering the true essence of the problem. The point is that this progress required engineers to question assumptions and dissuade stakeholders; without their involvement, the unnecessary features would have become part of the problem specification, “ossified” into its essence.&lt;/p&gt;&lt;/div&gt;&#xA;</description>
    </item>
  </channel>
</rss>
