<?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>Software-Architecture on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/tags/software-architecture/</link>
    <description>Recent content in Software-Architecture on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <copyright>2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Mon, 27 Aug 2018 09:22:18 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/tags/software-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Project architecture is not product architecture</title>
      <link>https://www.shafiq.in/blog/project-architecture-is-not-product-architecture/</link>
      <pubDate>Mon, 27 Aug 2018 09:22:18 +0000</pubDate>
      <guid>https://www.shafiq.in/blog/project-architecture-is-not-product-architecture/</guid>
      <description>&lt;p&gt;I spent a good chunk of last week designing the architecture for a new service. On paper it was clean — well separated concerns, sensible boundaries, tests covering the happy paths. I felt good about it.&lt;/p&gt;
&lt;p&gt;Then someone asked what this service was going to become in two years time, and I realised I had no idea. Not because the design was bad, but because I had never really thought about it beyond the project itself. I had optimised for getting something built, not for where it was going.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
