Code

Teams working with feature flags usually come to the conclusion that a large number of active flags isn’t necessarily a good thing. While each active feature flag in your system delivers some benefit, each flag also comes with a cost. I’m going to explain those costs, such as cognitive load and technical debt, and explain how to avoid them.

Feature flagging systems can sometimes become victims of their own success. The benefits of feature flagging along with the broad applicability of the technique can lead to rapid adoption within an organization, and pretty soon the number of active flags can start to feel overwhelming. One way to keep your feature flags manageable is to introduce a categorization system.

The concept of Serverless Computing, also called Functions as a Service (FaaS) is fast becoming a trend in software development. This blog post will highlight steps and best practices for integrating Split feature flags into a serverless environment.

Feature flags are a necessary part of your Continuous Delivery (“CD”) pipeline. In fact, as your team grows, you can’t do CD without feature flags. This article provides best practices on when to use feature flags.

Since joining Split, it has been clear that feature testing is the fundamental building block of our software development process. We deploy unit tests to validate discrete parts of business logic, end-to-end tests to monitor our APIs, automated usability testing to maintain our user experience, and entire network of bots…

In this episode we are covering how to write modular testing code, maximizing reusability so your framework can adapt quickly to changes.

There are two primary options for icon systems: scalable vector graphics (SVG) and icon fonts. When considering the best solution, a developer has to determine which is most performant, with the highest quality, at the lowest cost of development. Having compared these options at Split, we believe SVG icons are…

In the world of Selenium usability testing, many intermittent failures are caused by elements not showing up in time or not being enabled when the test tries to access it. Adding extra checks on your tests might slow down your suites, but it’s a small price to pay for reliability when coding for web or mobile SDK.

End to End (E2E) WebDriver Testing is a two-edged sword; it can be the hero, saving you a lot of time during regression testing and preventing faulty releases, or it can be the villain, slowing down the development and release process with flakey, hard to maintain and time-consuming suites that…