<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Featureflags on /dev/eric</title>
		<link>https://ericlim.dev/tags/featureflags/</link>
		<description>Recent content in Featureflags on /dev/eric</description>
		<generator>Hugo</generator>
		<language>en-GB</language>
		
		
		
		
			<lastBuildDate>Wed, 23 Sep 2026 17:45:00 +1200</lastBuildDate>
		
			<atom:link href="https://ericlim.dev/tags/featureflags/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Lessons from Consolidating Unleash Feature Flags</title>
				<link>https://ericlim.dev/posts/20260923t174500--lessons-from-consolidating-unleash-feature-flags/</link>
				<pubDate>Wed, 23 Sep 2026 17:45:00 +1200</pubDate>
				<guid>https://ericlim.dev/posts/20260923t174500--lessons-from-consolidating-unleash-feature-flags/</guid>
				<description>&lt;p&gt;I’ve spent the past week migrating Unleash feature flags from several projects&#xA;into one, mostly to clean them up and keep them in one place. Here’s what I was&#xA;dealing with.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Parent flags can’t depend on a flag in another project&lt;/li&gt;&#xA;&lt;li&gt;Segments can’t be shared across projects&lt;/li&gt;&#xA;&lt;li&gt;Visibility drops when one feature is spread over several projects&lt;/li&gt;&#xA;&lt;li&gt;Cross-team coordination gets expensive for the same reason&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Some of these have a simple fix. Removing the project scope from a segment (a&#xA;reusable bundle of constraints that any strategy can reference) makes it&#xA;available to every project. Others have none. A parent flag in one project&#xA;simply cannot reference a child in another. I’m sharing some stats and what I&#xA;learned along the way.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
