<?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>Experimentation on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/experimentation/</link>
    <description>Recent content in Experimentation on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Feb 2023 11:02:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/experimentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Feature Flags at Scale: Beyond the On/Off Switch</title>
      <link>https://blog.turboawesome.win/2023/02/feature-flags-at-scale-beyond-the-on/off-switch/</link>
      <pubDate>Tue, 28 Feb 2023 11:02:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2023/02/feature-flags-at-scale-beyond-the-on/off-switch/</guid>
      <description>Feature flags sound simple — toggle code on or off. At scale they&amp;#39;re a deployment primitive, an experimentation platform, a kill-switch infrastructure, and a source of technical debt. Here&amp;#39;s what a mature feature flag system looks like and how to avoid the traps.</description>
    </item>
  </channel>
</rss>
