<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Systems on Bill Glover</title>
		<link>https://old.bill.dev/tags/systems/</link>
		<description>Recent content in Systems on Bill Glover</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
			<managingEditor>hello@bill.dev (Bill)</managingEditor>
		
		
			<webMaster>hello@bill.dev (Bill)</webMaster>
		
		
		
			<lastBuildDate>Sun, 28 Sep 2025 22:27:35 +0100</lastBuildDate>
		
			<atom:link href="https://old.bill.dev/tags/systems/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Lessons from Drawing System Diagrams</title>
				<link>https://old.bill.dev/2023/03/31/lessons-from-drawing-system-diagrams/</link>
				<pubDate>Fri, 31 Mar 2023 17:42:21 +0000</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2023/03/31/lessons-from-drawing-system-diagrams/</guid>
				<description>&lt;p&gt;&lt;em&gt;Assumed Audience:&lt;/em&gt; anyone who has drawn a system or software diagram; architects, engineers, developers&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;I came across this list of &lt;a href=&#34;https://icepanel.medium.com/common-software-diagramming-mistakes-35dbf2864ef1&#34;&gt;common software diagraming mistakes&lt;/a&gt; by IcePanel and was reminded of the days when I used to spend much of my day explaining complex systems. Diagrams were always involved but not always successful. As a result, there are a few tips I&amp;rsquo;d add to the list.&lt;/p&gt;&#xA;&lt;h2 id=&#34;state-your-assumed-audience&#34;&gt;State your assumed audience&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;💡 Tip:&lt;/strong&gt; Clearly articulate your assumed audience for each diagram.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
