<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stylecop on Maceage's Blog</title><link>https://blog.maceage.com/tags/stylecop/</link><description>Recent content in Stylecop on Maceage's Blog</description><generator>Hugo</generator><language>en-au</language><copyright>© Graham Mace</copyright><lastBuildDate>Sun, 04 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.maceage.com/tags/stylecop/index.xml" rel="self" type="application/rss+xml"/><item><title>Copping Some Style</title><link>https://blog.maceage.com/posts/2024/copping-some-style/</link><pubDate>Sun, 04 Feb 2024 00:00:00 +0000</pubDate><guid>https://blog.maceage.com/posts/2024/copping-some-style/</guid><description>&lt;p&gt;&lt;small&gt;&lt;i&gt;(Originally drafted in November 2019 during my tenure at Xero. Republished here in February 2024 with updated context and removed proprietary references)&lt;/i&gt;&lt;/small&gt;&lt;/p&gt;&#10;&lt;p&gt;In a commercial environment, all documents (both internal and external) tend to follow a templated format: presentation decks, internal documents, email footers and internal systems, to name a few – even the software we produce tends to follow the same UI conventions to ensure the experience for end users is consistent.&lt;/p&gt;</description></item></channel></rss>