<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Design on Thomas Cothran</title><link>https://thomascothran.tech/tags/design/</link><description>Recent content in Design on Thomas Cothran</description><generator>Hugo</generator><language>en</language><copyright>2023, Thomas Cothran</copyright><lastBuildDate>Sun, 20 Aug 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://thomascothran.tech/tags/design/index.xml" rel="self" type="application/rss+xml"/><item><title>The Library Locker - An Antipattern</title><link>https://thomascothran.tech/2023/08/library-locker/</link><pubDate>Sun, 20 Aug 2023 00:00:00 +0000</pubDate><guid>https://thomascothran.tech/2023/08/library-locker/</guid><description>The library locker antipattern occurs when we try to add functionality to a library function, but do so without separating concerns.</description></item></channel></rss>