<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Visualisation on Andy Bulka</title>
		<link>https://abulka.github.io/tags/visualisation/</link>
		<description>Recent content in Visualisation on Andy Bulka</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Wed, 09 Sep 2026 12:38:38 +1000</lastBuildDate>
		
			<atom:link href="https://abulka.github.io/tags/visualisation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Annotating UML with Design Patterns as Visual Objects</title>
				<link>https://abulka.github.io/blog/2026/09/09/annotating-uml-with-design-patterns-as-visual-objects/</link>
				<pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://abulka.github.io/blog/2026/09/09/annotating-uml-with-design-patterns-as-visual-objects/</guid>
				<description>&lt;p&gt;Conventional UML has a blind spot. Once a diagram grows beyond a handful of classes, you can see all the classes and relationships perfectly well — but you have to &lt;em&gt;mentally recognise&lt;/em&gt; that &amp;ldquo;oh, these four classes are actually an Observer pattern&amp;rdquo;. The structure is visible; the &lt;em&gt;design intent&lt;/em&gt; is not.&lt;/p&gt;&#xA;&lt;p&gt;This post is about an idea I prototyped years ago and keep coming back to: treating the &lt;strong&gt;design pattern itself as a visual object layered on top of ordinary UML&lt;/strong&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
