<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>cogville</title>
    <link rel="self" type="application/atom+xml" href="https://cogville.site/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://cogville.site"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-08-04T00:00:00+00:00</updated>
    <id>https://cogville.site/atom.xml</id>
    <entry xml:lang="en">
        <title>Residuality Theory - First impression</title>
        <published>2026-08-04T00:00:00+00:00</published>
        <updated>2026-08-04T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://cogville.site/writing/residuality-first-impression/"/>
        <id>https://cogville.site/writing/residuality-first-impression/</id>
        
        <content type="html" xml:base="https://cogville.site/writing/residuality-first-impression/">&lt;p&gt;I just finished the book &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;leanpub.com&#x2F;residuality&quot;&gt;Residues: Time, Change, and Uncertainty in
Software Architecture.&lt;&#x2F;a&gt; by &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;www.linkedin.com&#x2F;in&#x2F;barry-o-reilly-b924657&#x2F;&quot;&gt;Barry
O’Reilly&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;It made me think.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;em&gt;Right now&lt;&#x2F;em&gt; I am thinking it is probably the most interesting book on
software architecture and our profession as architects or leaders in
software I have read in a long while.  It made me recognise myself,
challenges I have had and doubts I have held. More than anything it
gave me an eagerness to try out what it describes.&lt;&#x2F;p&gt;
&lt;p&gt;This reminds me of when I first learned TDD more than twenty years
ago. In that I imagine it will work similarly as a way to &quot;get
started&quot; when faced with the vastness of (then design-) options, not
get stuck in analysis paralysis. Especially the stress(or) testing and
contagion analysis spoke to me as something that I have had problems
articulating or repeating but having some kind of notion of in my
head. Never had it expressed so clearly.&lt;&#x2F;p&gt;
&lt;p&gt;It also gave me - or at least reignited - hope for my continued
curiosity for my profession. It is the most &quot;hopeful&quot; book about
software development and software architecture as a profession I have
read in a long while. Both in the way that it portrayed a reasoned,
philosophically interesting idea about what software architecture can
be and how it can continue to be FUN! It also made me
feel... supported. Not sure if that is the right word. But I
felt... not so alone, that there are both these &quot;crazy&quot; ideas left to
explore and that there are so many established but ungrounded
practices out there that I want to continue challenging.&lt;&#x2F;p&gt;
&lt;p&gt;Thank you Barry!&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
