5 ms·

We've used LaunchDarkly (LD) for about a year now. We previously used our own Feature Flag library built by our CTO: https://www.npmjs.com/package/dipswitch htt

We've used LaunchDarkly (LD) for about a year now. We previously used our own Feature Flag library built by our CTO: https://www.npmjs.com/package/dipswitch https://www.npmjs.com/package/dipswitch. LD provided a lot more, and continues to release new features that would've been much more expensive for us to build vs. buy here. We’ve been so pleased w/ LD that we agreed to do a case study with them if you want to take a gander: https://launchdarkly.com/casestudies/lanetix.html https://launchdarkly.com/casestudies/lanetix.html Also, we implemented most of LD in a 24-hour quarterly hackathon we hold at my company: https://engineering.lanetix.com/2016-02-22/how-lanetix-does-shipit-day/ https://engineering.lanetix.com/2016-02-22/how-lanetix-does-... Hope this helps!

dandemeyere 10y ago
We used to have our own feature flag library built by our CTO as well! We (thredUP) recently switched to Split (http://www.split.io/ http://www.split.io/) and it's been incredibly helpful for our team of 25 engineers. Slow controlled roll-outs, short circuit broken features without a deploy through their dashboard, and we actually use them for A/B tests as well since they have an impression data pipeline and A/B tests are so similar to feature flagging. Definitely one of the smartest "buys" we've made in our last 4-5 "buy vs. build" discussions.
automatwon 10y ago
LD provided a lot more ... that would have been more expensive for us to build vs buy we implemented most of LD in a 24-hour quarterly hackathon we hold What's the breakdown of 'most' vs the remaining? 80/20? Alternatively, if 'most' was implemented in 24 hours, how long would it take to implement the rest? From these two statements, I get the impression that either (1) LD is cheap to buy to begin (2) 'most' should be taken with a dash of salt
automatwon 10y ago
LD provided a lot more ... that would have been more expensive for us to build vs buy? we implemented most of LD in a 24-hour quarterly hackathon we hold What's the breakdown of 'most' vs the remaining? 80/20? Alternatively, if 'most' was implemented in 24 hours, how long would it take to implement the rest? From these two statements, I get the impression that either (1) LD is cheap to buy to begin (2) 'most' should be taken with a dash of salt

dandemeyere 10y ago

We used to have our own feature flag library built by our CTO as well! We (thredUP) recently switched to Split (http://www.split.io/ http://www.split.io/) and it's been incredibly helpful for our team of 25 engineers. Slow controlled roll-outs, short circuit broken features without a deploy through their dashboard, and we actually use them for A/B tests as well since they have an impression data pipeline and A/B tests are so similar to feature flagging. Definitely one of the smartest "buys" we've made in our last 4-5 "buy vs. build" discussions.

automatwon 10y ago

LD provided a lot more ... that would have been more expensive for us to build vs buy we implemented most of LD in a 24-hour quarterly hackathon we hold What's the breakdown of 'most' vs the remaining? 80/20? Alternatively, if 'most' was implemented in 24 hours, how long would it take to implement the rest? From these two statements, I get the impression that either (1) LD is cheap to buy to begin (2) 'most' should be taken with a dash of salt

automatwon 10y ago

LD provided a lot more ... that would have been more expensive for us to build vs buy? we implemented most of LD in a 24-hour quarterly hackathon we hold What's the breakdown of 'most' vs the remaining? 80/20? Alternatively, if 'most' was implemented in 24 hours, how long would it take to implement the rest? From these two statements, I get the impression that either (1) LD is cheap to buy to begin (2) 'most' should be taken with a dash of salt