<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software Architecture on Dinko Pehar</title>
    
    
    
    <link>/topics/software-architecture/</link>
    <description>Recent content in Software Architecture on Dinko Pehar</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0200</lastBuildDate>
    
	<atom:link href="/topics/software-architecture/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Software Architecture Design</title>
      <link>/digital-garden/software-architecture/software-architecture-design/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0200</pubDate>
      <guid>/digital-garden/software-architecture/software-architecture-design/</guid>
      <description>
        
          
          
          
        
        
        &lt;p&gt;Software architecture design is the work of deciding a system&amp;rsquo;s major
boundaries, responsibilities, data flow, and operational constraints before
implementation details take over.&lt;/p&gt;
&lt;p&gt;Questions to explore:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Which decisions are difficult or expensive to change later?&lt;/li&gt;
&lt;li&gt;What should a design document make explicit before coding starts?&lt;/li&gt;
&lt;li&gt;How can a system stay simple while leaving room for likely change?&lt;/li&gt;
&lt;/ul&gt;

        
        </description>
    </item>
    
  </channel>
</rss>