The effects of burnout can be significant for any software development organization, large or small. In this blog post, we discuss how burnout can be alleviated with an agile workflow powered by feature flags, a robust feature experimentation platform and incremental feature rollouts using continuous delivery.
The shift-left testing emphasizes test execution early and often, providing rapid feedback to development teams for each new code commit. Shift-right extends application testing into the production environment. Learn about the benefits and recommended best practices of using feature flags to support Testing in Production.
This is one post in a series about managing the breakup of a monolithic architecture into a small service. In the first post of the series we looked at some fundamental techniques which allowed us to perform this sort of broad architectural shift as a series of small, safe steps. We started off…
This blog posts describes the sequence of changes a team can use to extract a chunk of functionality out from a monolith while continuing to deliver features and functionality in parallel.
With Split’s improved invite flow it is now easier to invite your entire team and assign teammates to groups at the time of invitation. You can now invite multiple teammates at once and assign them individually or in bulk to groups, simplifying your team’s onboarding to Split.
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.
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.