<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Delivery on Nalar</title>
    <link>https://nalar.dev/tags/delivery/</link>
    <description>Recent content in Delivery on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/delivery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Managing Feature Flags as Temporary Code</title>
      <link>https://nalar.dev/managing-feature-flags-as-temporary-code/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/managing-feature-flags-as-temporary-code/</guid>
      <description>&lt;p&gt;A feature flag can make a risky change easier to release. Instead of making deployment and exposure happen at the same moment, the team can deploy code while keeping new behavior disabled, enable it for a limited audience, observe the result, and turn it off without rebuilding the application.&lt;/p&gt;&#xA;&lt;p&gt;That flexibility has a cost. Every flag introduces another condition that can affect behavior. If old flags remain indefinitely, developers must reason about combinations that no longer serve a useful purpose.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
