<?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>Dependencies on orndorff.dev</title>
    <link>https://orndorff.dev/tags/dependencies/</link>
    <description>Recent content in Dependencies on orndorff.dev</description>
    <generator>Hugo -- 0.138.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 03 Jun 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://orndorff.dev/tags/dependencies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Monorepos: The Secret Weapon Against Tech Debt</title>
      <link>https://orndorff.dev/posts/monorepos-rule/</link>
      <pubDate>Sat, 03 Jun 2023 00:00:00 +0000</pubDate>
      <guid>https://orndorff.dev/posts/monorepos-rule/</guid>
      <description>&lt;h1 id=&#34;monorepos-the-secret-weapon-against-tech-debt&#34;&gt;Monorepos: The Secret Weapon Against Tech Debt&lt;/h1&gt;
&lt;p&gt;Hold on to your (code)bases, because we&amp;rsquo;re about to dive into the thrilling world of monorepos and their unexpectedly effective role in managing tech debt!&lt;/p&gt;
&lt;h2 id=&#34;choose-your-fighter&#34;&gt;Choose Your Fighter&lt;/h2&gt;
&lt;h3 id=&#34;monorepo-the-one-repo-to-rule-them-all&#34;&gt;Monorepo: The One Repo to Rule Them All&lt;/h3&gt;
&lt;p&gt;Monorepos are like a software development Swiss Army knife. In a monorepo setup, you&amp;rsquo;ve got one repository that manages all code and services with shared build tooling and common dependencies. It&amp;rsquo;s the Beyoncé of repositories, and it&amp;rsquo;s got a fan base like Google and Facebook, which definitely says something.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
