<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Veysel Ozdemir on Medium]]></title>
        <description><![CDATA[Stories by Veysel Ozdemir on Medium]]></description>
        <link>https://medium.com/@ozdemirv?source=rss-4f396f457470------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tQD1edcfT94nzmbd</url>
            <title>Stories by Veysel Ozdemir on Medium</title>
            <link>https://medium.com/@ozdemirv?source=rss-4f396f457470------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:48:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ozdemirv/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[It’s Time to Stop Saying “Software Architecture”]]></title>
            <link>https://ozdemirv.medium.com/its-time-to-stop-saying-software-architecture-f38653a40cdf?source=rss-4f396f457470------2</link>
            <guid isPermaLink="false">https://medium.com/p/f38653a40cdf</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Veysel Ozdemir]]></dc:creator>
            <pubDate>Sat, 06 Aug 2022 19:01:09 GMT</pubDate>
            <atom:updated>2022-08-19T08:16:17.206Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*QA5cOiyKn-iXFVlxZYOssA.png" /><figcaption>A system diagram vs map of a city</figcaption></figure><p>“Architecture” is a very common anlogy used in software engineering, and a very successful one. So successful, that we have “architect” as a role in software world. It’s cool to be an architect! Anyone remembers “The Architect” in The Matrix? Yes it’s cool but, <strong>why </strong>do we think in terms of architecture?</p><ul><li>Maybe because both are related to “building” something.</li><li>There is a design bit. Maybe that’s the reason.</li><li>It’s not exactly engineering, there’s an “art” bit (even black art to some).</li></ul><p>All these are OK, but still not good enough. It fails as an analogy to be useful. There are many places it doesn’t work.</p><h3>Where does architecture fail?</h3><p>At this point you probably understood. I don’t like the term software architecture. We “people who make software” and them “people who design buildings” both draw diagrams to convey our ideas. I think the similarity ends pretty much there.</p><p>Take the <strong>production process</strong>. Construction is a “waterfall” process. An architect is a person who creates designs and detailed blueprints, before the construction work, so that engineers will follow to the milimetre and implement. No sane person makes software like that anymore.</p><p>Or take the <strong>relationship between “business” and “developer”</strong>. It assumes that an architect is necessary to bridge the gap between business and developers, thus represses everyone to their own places.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*W5_dNx5tKPXbi-447RDI_A.png" /><figcaption>A system diagram vs sketch of a building</figcaption></figure><p>These are the things that come to my mind when I think of a software system:</p><ul><li>It’s made of programs that work / opereate together.</li><li>These programs use each other, sometimes they are mutually dependent.</li><li>Different groups of people design, make and run these programs.</li><li>Over time it evolves. “<strong>Time</strong>” and “<strong>layers that time bring</strong>” have a huge effect in software systems.</li></ul><p>If anything they make up an “evolving ecosystem” rather than being a “mechanism” or a done and finished building. <strong>So, I have a better suggestion: 👇</strong></p><h3>A software system is actually, like a city</h3><p>I know what you think by this point, it’s equally cheesy 😁 but, some cheese are better than others. <a href="https://youtu.be/C906lbkcYug">If you don’t believe me listen to The Smiths</a>.</p><p><strong>Both evolve</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*2ojheJHunYAqtSy5vJNO1A.png" /><figcaption>From village to a mega city</figcaption></figure><p>As an ecosystem it changes and grows. You start with a single dwelling, then you grow it to be a village. It goes on:</p><p>Dwelling &gt; Vilalge &gt; Town &gt; City &gt; Metropolitan Area &gt; Country/Empire</p><p>Making of it never ends. It changes over time, and generally grows.</p><p><strong>Old and new live together</strong></p><figure><img alt="Photo of Derby Cathedral Quarter" src="https://cdn-images-1.medium.com/max/602/1*az1f2PsbR4rQhi21Y-uPuA.png" /><figcaption>Old and new buildings together</figcaption></figure><p>This is a photo of Derby Cathedral Quarter (<em>taken from </em><a href="https://dcms.shorthandstories.com/DerbyCathedralQuarter/index.html"><em>https://dcms.shorthandstories.com/DerbyCathedralQuarter/index.html</em></a>). It shows a very new building standing side by side with a very old building together. Certainly, they share the same infrastructure in the quarter and make up the quarter as a whole.</p><p>As the system evolve over time, old and new live together. This is true both for infrastructure and superstructure. When you want to make changes you see layers and layers of different implementations, libraries, <strong>styles and decisions of people past</strong>.</p><p>Goes without saying, as you do things, you leave your own mark along the way.</p><p><strong>Posh vs Poor</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*RkxBQYvQqOkKLOmTSlgxfw.png" /><figcaption>Kensington (rich) vs Kirkdale (poor)</figcaption></figure><p>Just like <strong>posh neighbourhoods</strong>, there are hot projects where everyone wants to work on. Investments are made there, best new tech is always there.</p><p>There are <strong>stable suburbs</strong>, boring but life flows in its own rhythm.</p><p>And, there are <strong>deprived neighbourhoods</strong>. Unloved, poor, old, no one fancy lives there. No investment, no new development.</p><p><strong>Both have scary places</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*emZ0q0q8tosWKhBmQi_hZw.png" /><figcaption>A dark alleyway, similar to a scary, dangerous but still functional application</figcaption></figure><p>Dark alleyways, rough neighbourhoods where law don’t apply. Old convoluted fragile programs that you’re afraid to touch let alone look at the code. No one wants to go there.</p><p>Unless of course you’re Batman 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*1J3ZQiTnJCMwS5mgHGOKSw.png" /></figure><p><strong>Migration / Gentrification</strong></p><p>And sometimes, deprived neighbourhoods sit on a goldmine and they cannot extract that value. We want to upgrade them, with better infrastructure, better buildings, better roads and transport links, newer frameworks, languages, CI/CD pipelines etc. etc.</p><p>Neither gentrification nor migration projects are easy. There is human cost, culture clash, unintended consequences, results falling short of the promise. Nevertheless we keep on doing them and for a reason. We’re all learning to do it better.</p><p>Cities, landscapes never stop, they always evolve just like our software systems. There are many people pumping life into them. They serve many purposes and there are many ways to design and run a city / software system.</p><p>I can go on and on. The more I look the more similarities I see. However, I’m sure if I look the other way round there are many differences too.</p><p>My hope is, one day in the future, our field will have enough history and stories of its own that we won’t need analogies to think about it. Until then, we need to switch to a better analogy than architecture, that allows us to think about coexistence, time/history, people factors, governance and many other things in our software ecosystems. This is why “city” is a better metaphor when thinking about softare systems.</p><p><em>This text is based on a lightning talk I did to my colleageues at </em><a href="https://www.moneysupermarket.com/"><em>MoneySuperMarket</em></a><em>. It is a silly/fun try to have a go at the “architecture” analogy in the software world. I tried to come up with a better one.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f38653a40cdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>