Lindsay Brunner, Adil Aijaz, Pato Echague, Trevor Stuart
This week we are excited to announce that we have closed a $33m Series C, led by Comcast Ventures with new investors including Microsoft’s M12, 01 Advisors, Atlassian, and ServiceNow, as well as previous investors, Accel, Lightspeed Venture Partners, and Harmony Venture Partners. We see this new round of investment…
Software development has an impact gap: 80% of features have no or negative impact.
With feature flags as a foundation for controlled rollout, dev teams can measure and experiment as they deliver new features.
When versioning your API, consider the tradeoffs between distinct microservices and feature flags.
Staging environments aren’t great reflections of reality. Instead, investing in CI/CD, feature flags, and QA can skip your code straight to production.
Feature launches in leading engineering teams increasingly look like a ramp rather than a one time switch, going through dogfooding, debugging, max power ramp, scalability and learning phases.
If your release train is moving slower than you would like, take a look at these three essential ingredients you should have.
Col. John Boyd came up with a theory of warfare called the OODA loop (Observe, Orient, Decide, Act). Companies compete through OODA loops in product. Instead of air-to-air combat, a company that is better at “rapidly delivering valuable software” has a better chance for overcoming competition.
Following up from the excellent post by Pete Hodgson on Retiring Your Flags, and his presentation at the Meetup we recently sponsored, I wanted to dive into how Split plays a role in managing your flag debt. Feature flags (aka toggles, flips, gates, or switches) are a software delivery concept…
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.