From 8c78783585c5da55dfa6ddf517ca4167959cdf4c Mon Sep 17 00:00:00 2001 From: Yash Malik Date: Thu, 24 Jul 2025 17:34:33 +0530 Subject: [PATCH] docs: Update what-is-a-feature-flag.mdx Fixed link to the State of DevOps Report --- website/docs/topics/what-is-a-feature-flag.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/topics/what-is-a-feature-flag.mdx b/website/docs/topics/what-is-a-feature-flag.mdx index 98523b37a5..aeb8a49616 100644 --- a/website/docs/topics/what-is-a-feature-flag.mdx +++ b/website/docs/topics/what-is-a-feature-flag.mdx @@ -14,7 +14,7 @@ In this guide, we’ll introduce you to the basics of feature flags and why so m *The easiest way to explain why developers use feature flags is to understand the story of why [Ivar Østhus](https://github.com/ivarconr), our CTO, created the Unleash feature flag service in the first place. Here's Ivar in his own words:* -> In 2014, I was working as a software developer at FINN.no, Norway’s largest online marketplace. Getting new features into production was a pain, so, as a developer, I looked around and wondered if I could write some code to make it easier. My initial goal was to protect features under development, allowing our team to transition to [trunk-based development](https://www.getunleash.io/blog/how-to-implement-trunk-based-development-a-practical-guide)—a practice recommended according to the [State of DevOps Report](https://www.getunleash.io/blog/guide-to-feature-flags#:~:text=State%20of%20DevOps%20Report). +> In 2014, I was working as a software developer at FINN.no, Norway’s largest online marketplace. Getting new features into production was a pain, so, as a developer, I looked around and wondered if I could write some code to make it easier. My initial goal was to protect features under development, allowing our team to transition to [trunk-based development](https://www.getunleash.io/blog/how-to-implement-trunk-based-development-a-practical-guide)—a practice recommended according to the [State of DevOps Report](https://cloud.google.com/blog/products/devops-sre/announcing-the-2023-state-of-devops-report). > > Even back at that time, we embraced agility with an automated delivery pipeline which made fixing bugs a breeze, but frequent feature releases? Not so much. Building features takes time, and waiting weeks for production testing felt wasteful. > We used feature branches, a common approach, to isolate unfinished features. However, this created a tangled web of problems: @@ -214,4 +214,4 @@ If you want to learn more about how to implement feature flags at scale, check o - [Feature Flag Tutorials](/feature-flag-tutorials/use-cases/gradual-rollout) - [Best practices for using feature flags at scale](./topics/feature-flags/best-practices-using-feature-flags-at-scale) - [Best practices for building and scaling feature flags](./topics/feature-flags/feature-flag-best-practices) -- [Try Unleash for Free](https://www.getunleash.io/pricing) \ No newline at end of file +- [Try Unleash for Free](https://www.getunleash.io/pricing)