How we deploy new features

Recent discussions have highlighted strategies for rolling out new features, with Ross at Flickr using flags and flippers and Forrst utilizing user buckets to fine-tune their implementations. These methods are praised for their simplicity and adaptability. Initially, user feature flags were employed to grant beta access for the Orgs launch, but concerns arose about enabling the feature for entire teams, leading to conditional UI statements. Frequent deployments can clutter commit histories with minor tweaks, so a shift towards using Redis for configuration management was explored. This approach allowed for traffic distribution to new servers and easy bug fixes by adjusting Redis values without redeployment. Redis' Set commands are also considered for potential bucket management, demonstrating its versatility in feature rollout processes.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.