<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dependency Management on Nalar</title>
    <link>https://nalar.dev/tags/dependency-management/</link>
    <description>Recent content in Dependency Management on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/dependency-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Managing Dependencies as Explicit Boundaries</title>
      <link>https://nalar.dev/managing-dependencies-as-explicit-boundaries/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/managing-dependencies-as-explicit-boundaries/</guid>
      <description>&lt;p&gt;Third-party libraries save engineering time, but every dependency also adds a contract that your software must live with. That contract includes more than function signatures. It can include configuration formats, exceptions, lifecycle rules, performance characteristics, release policies, and assumptions that spread through application code.&lt;/p&gt;&#xA;&lt;p&gt;Dependency management is therefore partly a software design problem. The goal is not to avoid dependencies. It is to make important dependencies explicit, contained, and inexpensive to change.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
