<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Release Engineering on Nalar</title>
    <link>https://nalar.dev/tags/release-engineering/</link>
    <description>Recent content in Release Engineering on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/release-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Feature Flags Without Long-Lived Technical Debt</title>
      <link>https://nalar.dev/feature-flags-without-technical-debt/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/feature-flags-without-technical-debt/</guid>
      <description>&lt;p&gt;Feature flags decouple code deployment from feature release. A team can deploy dormant code, enable it for internal users, roll it out gradually, and disable it without rebuilding the application.&lt;/p&gt;&#xA;&lt;p&gt;The cost is hidden control flow. Every long-lived flag creates another possible system configuration, and interacting flags multiply those configurations quickly.&lt;/p&gt;&#xA;&lt;p&gt;The engineering goal is therefore not &amp;ldquo;use flags everywhere.&amp;rdquo; It is to make each flag temporary, observable, and owned.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
