Zayyad Muhammad Sani

Let's say you've heard about the benefits of using feature flags for gradual feature rollouts, and you're ready to adopt them in your organization. The next step would be deciding whether to "build or buy."

If you choose to develop your feature flagging tool, you'll need to figure out how to make it fetch, evaluate, and manage feature flags. If you want to use a third-party tool, you might have to learn and unlearn different APIs as you search for the right one.

Challenges like these inspired the creation of OpenFeature, a CNCF (Cloud Native Computing Foundation) project that aims to standardize feature flagging.

Suppose you come up with an idea to improve the conversion rates on your website. You could implement the idea and roll out the changes to all users. But what happens if the idea is only good on paper and fails in reality? In cases like this, conducting an A/B test is an excellent way to validate your idea.

In the upcoming sections, we'll learn how to set up an A/B test using ConfigCat feature flags and visualize the test's data in Google Analytics.

As you might have heard by now, the tech world is undergoing massive layoffs due to the looming recession. Big tech companies like Twitter, Meta, Google, and Amazon have all announced massive job cuts in the past few months. Software developers are on the receiving end in 2023, accounting for 20% of layoffs, according to data from workforce intelligence firm Revelio Labs.

Apart from the stress and anxiety it causes employees who were let go, layoffs can disrupt the rhythm of development teams and impact how projects move forward. The developers that survive layoffs are expected to keep everything running smoothly despite their smaller numbers. They'll have to explore strategies that will allow them to continue working efficiently and produce high-quality software without overworking themselves.

As the world increasingly becomes digital, we rely on software to solve problems that pop up in everyday life. However, because traditional software development is complex and time-consuming, there aren't enough software developers to meet the high demand for software products. No-code and low-code tools offer a solution to this problem by allowing people to create software and multimedia content and perform complex tasks without writing code.

Feature flags are becoming a prominent part of DevOps practices and for good reason. They allow you to turn features in your live application on or off without redeploying code. You might think that something so powerful would require some rocket science-level programming to implement, but you'd be surprised to know that, at their core, feature flags are booleans and if-then-else statements.

Okay, that's an oversimplification of things, but it's true. And while there are different ways of implementing feature flags, they all share this common core. That said, let's take a broader look at feature flags and their uses in modern software development.

Government agencies, with their strict security requirements, often face difficulties in fully embracing DevSecOps practices. Balancing the need for rapid feature releases with robust security measures poses a challenge. Feature flags offer a promising solution in this context. By seamlessly integrating into DevOps and DevSecOps pipelines, they can empower government agencies to effectively manage feature releases while maintaining high levels of security.

If there's one thing we don't tolerate here at ConfigCat, that's terrible customer support. Our customers are important to us, and we try our best to provide all the help we can so that they get the best out of our services. In this article, we'll look at how we ensure that our customers have a hassle-free experience when using our service.

Can naming feature flags be hard?

Yes. Just like variables in programming, naming feature flags can get tricky if you don't follow a naming standard. When feature flags don't have good names, it can be difficult for people using them to remember what they do. In this article, we'll see a few naming conventions we can use for feature flags.

Creating software products is a highly collaborative process nowadays. Developers, designers, product managers, marketers, and many others all work together to bring software to life and ensure a smooth experience for customers.

Though developers are responsible for building new features, the control of releasing these features might be better in the hands of people that are outside of engineering teams. We can give these people control with the help of feature flags.

A/B testing answers the question: "Which of these versions will bring me better results, A or B?". It allows you to test two variations of a page to see which has a more positive impact. This could mean increased sign-ups for a landing page, more purchases on an e-commerce store, or even smoother user processes in an app. It all depends on what you want to improve. How does A/B testing work though?