Inspired by Markdown, a plain text formatting syntax by @gruber, readable and consistent, we wanted to reflect on a vision making feature flagging as frictionless as possible.
We launched Bucket MCP last week and got featured in The Leaderboard.
@aaronoleary put it elegantly:
Whether you're using @Cursor, @Augment Code, or @Windsurf, you can just tell it what you want flagged, and the MCP server handles it. So instead of context-switching to write config files or CLI commands, you just prompt: flag the download button. That s it.
Meow there! Last week was launch week at Bucket, wrapping up a month of shipping features to make feature flagging a fast, joyful experience for SaaS developers.
@roncohen and I are building @Bucket to enable developers in SaaS to ship the right features, faster.
Before that, we co-founded @Opbeat , got acquired by @ElasticSearch , ran the 100+ Observability team, quit, co-founded another devtool company, raised VC funding again, hired a wonderful team (remote).
In software engineering, trunk-based development (TBD) is a strategy to manage git workflows that favours merging commits into the `main` branch even before the feature is fully complete, instead of the git flow that favours working on long-lived branches until features are 100% complete. TBD or GitFlow: What's your current developer workflow?
