<?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>Architecture on Jake Worth</title>
    <link>https://jakeworth.com/tags/architecture/</link>
    <description>Recent content in Architecture on Jake Worth</description>
    <image>
      <title>Jake Worth</title>
      <url>https://jakeworth.com/twittercard.png</url>
      <link>https://jakeworth.com/twittercard.png</link>
    </image>
    <generator>Hugo -- 0.159.1</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 01 Feb 2026 12:46:52 -0500</lastBuildDate>
    <atom:link href="https://jakeworth.com/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Unabstract an Abstraction</title>
      <link>https://jakeworth.com/posts/how-to-unabstract-an-abstraction/</link>
      <pubDate>Sun, 01 Feb 2026 12:46:52 -0500</pubDate>
      <guid>https://jakeworth.com/posts/how-to-unabstract-an-abstraction/</guid>
      <description>&lt;p&gt;Abstractions in code are easy to add and challenging to remove. Sometimes we feel stuck with them. But the good news is, you can back out of almost any abstraction with the right mindset.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Decoupling Design From Engineering</title>
      <link>https://jakeworth.com/posts/decoupling-design-from-engineering/</link>
      <pubDate>Thu, 29 Aug 2024 11:55:49 -0400</pubDate>
      <guid>https://jakeworth.com/posts/decoupling-design-from-engineering/</guid>
      <description>&lt;p&gt;Often, when you work as an engineer on a small team, you don&amp;rsquo;t have dedicated designers on staff. How can you deliver beautiful, intuitive software without designers? Here&amp;rsquo;s a trick that helps me: decoupling my design work from my engineering work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Naive Implementation: The Art of Artless Programming</title>
      <link>https://jakeworth.com/posts/naive-implementation/</link>
      <pubDate>Thu, 23 Jun 2022 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/naive-implementation/</guid>
      <description>&lt;p&gt;A naive implementation is a programming technique that prioritizes imperfect
shortcuts for the sake of speed, simplicity, or lack of knowledge.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PostgreSQL Polymorphism</title>
      <link>https://jakeworth.com/posts/postgresql-polymorphism/</link>
      <pubDate>Mon, 30 May 2022 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/postgresql-polymorphism/</guid>
      <description>&lt;p&gt;Scenario: you need a database record that can belong to one record or another, but not
both. Polymorphism and exclusivity. One approach is to create a polymorphic-style association at
the data layer. By doing so, you&amp;rsquo;ll get data integrity built in, rather than
trusting it will be enforced by each tenant at the application layer.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Make Renames Easy</title>
      <link>https://jakeworth.com/posts/make-renames-easy/</link>
      <pubDate>Tue, 22 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/make-renames-easy/</guid>
      <description>&lt;p&gt;Names in software are hard. But what&amp;rsquo;s worse than a bad name? Sticking with it
because you can&amp;rsquo;t change it. I want us all to be able to effortlessly and
fearlessly fix bad names. That&amp;rsquo;s the topic of this post.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Write Better Code by Knowing When Not To Refactor</title>
      <link>https://jakeworth.com/posts/when-should-i-not-refactor/</link>
      <pubDate>Thu, 26 Aug 2021 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/when-should-i-not-refactor/</guid>
      <description>&lt;p&gt;When I review code, I sometimes request that refactoring changes be removed.
Even when I think the changes are are objective improvements, and even when
they support my personal preferences. My reasoning? Refactors are not free.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Augmenting an Object With the Proxy Pattern</title>
      <link>https://jakeworth.com/posts/proxy-pattern/</link>
      <pubDate>Fri, 26 Feb 2021 00:00:00 +0000</pubDate>
      <guid>https://jakeworth.com/posts/proxy-pattern/</guid>
      <description>&lt;p&gt;Let&amp;rsquo;s look at the proxy pattern in Ruby.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
