<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Plantuml on Maceage's Blog</title><link>https://blog.maceage.com/tags/plantuml/</link><description>Recent content in Plantuml on Maceage's Blog</description><generator>Hugo</generator><language>en-au</language><copyright>© Graham Mace</copyright><lastBuildDate>Sun, 03 Mar 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.maceage.com/tags/plantuml/index.xml" rel="self" type="application/rss+xml"/><item><title>Codifying Architecture: Diagrams as Code</title><link>https://blog.maceage.com/posts/2024/codifying-architecture/</link><pubDate>Sun, 03 Mar 2024 00:00:00 +0000</pubDate><guid>https://blog.maceage.com/posts/2024/codifying-architecture/</guid><description>&lt;p&gt;&lt;small&gt;&lt;i&gt;(Originally drafted in August 2019 during my tenure at Xero. Republished here in March 2024 with updated context and removed proprietary references)&lt;/i&gt;&lt;/small&gt;&lt;/p&gt;&#10;&lt;p&gt;Engineers love writing code. There&amp;rsquo;s nothing quite like instantly seeing the fruits of your labour appear on a screen – immediate feedback and the joy of getting something working.&lt;/p&gt;&#10;&lt;p&gt;Engineers, however, tend to hate writing documentation. It takes time, it&amp;rsquo;s seen as overhead to &amp;ldquo;real work,&amp;rdquo; and so it falls by the wayside. The next engineer to come along is told: &lt;em&gt;&amp;ldquo;Oh, that&amp;rsquo;s out of date – just look at the &amp;lsquo;self-documenting&amp;rsquo; code instead.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>