Dave Karow

If you are in Chicago or can travel there, check out @GOTOchgo May 22-24. @GOTOcon shows are well run by a warm and hospitable team & always feature top-notch technical speakers on various topics. Here's a query for videos of the talks I've given at GOTO: google.com/search?q=youtu…

@mipsytipsy @monkchips Two years after coining the term, @monkchips summed up the echos of the idea here: redmonk.com/jgovernor/2020…

And of course there's @monkchips, coiner and popularizer of progressive delivery. Who else deserves credit when it comes to modern release practices? I'll make sure and link their names to the piece on Monday. Apologies for not asking beforehand. ☺️✌️

Hey, I am hearing through the grapevine that I should have cited or credited some of the folks who did a lot of work in this area, and this is super true!! It looks like we have @LaunchDarkly to thank for "separate deploys from releases", and I know @wiredferret did a ton there.

@jeremydavis @housecor @SplitSoftware Here’s the link to doc page for Rollout Board for anyone following along. help.split.io/hc/en-us/artic…

@jeremydavis @housecor The Rollout Board in @SplitSoftware calls them "Ready to Cleanup" and has a built-in query that calls attention to them. Still, having them march slowly toward you moaning "brains!" could have it's appeal too 🤷‍♂️

Problem: Feature flags are handy, but it’s easy to forget to remove them later. This leads to needless overhead, complexity, and risk. Solution: Write an automated test that fails if the flag still exists after a given date.

Interview with @davefarley77 is youtu.be/mjoBw1utFAY and the Progressive Delivery talk I gave is youtu.be/cfCmJtkUTCA

Hey ⁦@afitnerd⁩ check out the t-shirt ⁦@davefarley77⁩ is wearing in this interview about the value of real #ContinousDelivery. Fellow PacMan fan it seems! Love the framework you laid so I could do my How PacMan Taught Me To Love Progressive Delivery talk a while back.

@LaunchDarkly @TheTeaNerd @semanticart @qrush Pretty sure the first time I saw it was when @mipsytipsy posted it.

@TheTeaNerd @semanticart @qrush we NEED to find the source of this 😂👀

I'm convinced Feature Flags are one of the best tools you have to mitigate risk. Roll something out to 1% of users and your bug tracker and alerting goes wild? Guess what? 99% of your users never had an issue. 😎 You should be using Feature Flags more.

@Codydearkland @LaunchDarkly @ronnyk NP. Your videos are always well-organized, showing a lot of up-front planning. I was surprised to see that segment in there.

@davekarow @LaunchDarkly @ronnyk Thanks for the feedback Dave.

@Codydearkland @LaunchDarkly @ronnyk "split" pun not intended, but I'll take it 'cause it helps explain why the place where I hang my hat is called @SplitSoftware. Causal analysis is in our bones :-)

@Codydearkland @LaunchDarkly Hey Cody, what you describe in the first half of your video is actually Blue/Green, not A/B. You can't conduct an A/B test by sending 100% of traffic to B. Without a split of traffic (50/50 or otherwise), there is no way to compare A and B performance. Check out @ronnyk for more.

🥑New Avocados Weekly is out - developeravocados.substack.com/p/creating-sur… 📝Content from @rosegoldlining, @remotesynth, @andypiper, @janackeh, @blackgirlbytes, @saltnburnem, @wesley83, @jasonhand, @daedtech, @kamranayub, @SlashDataHQ & @gemanor 📚CFPs from @infobipshift, @pyconlt & @BeerCityCode

@sesteva @patricioe @ph1 @SplitSoftware The motherlode of SDK docs, including both client and server SDKs, examples, and more, starts here: help.split.io/hc/en-us/categ…

@sesteva @patricioe @ph1 @SplitSoftware 2/2: For example here is that section from JavaScript SDK docs: #using-the-sdk" target="_blank" rel="nofollow noopener">help.split.io/hc/en-us/artic… - Using the SDK --Basic use --Shutdown --Multiple evaluations at once --Attribute syntax --Binding attributes to the client --Get Treatments with Configurations

@patricioe @ph1 @SplitSoftware Is there a document on splits local evaluation workflow ?

@ph1 @patricioe @SplitSoftware Those who haven’t gone that route try to shift the conversation to whether the evaluation rules are stored locally. That’s a red herring. Rules or not, everyone’s local app code must contain “if flag evaluates to x, do y” so the list of x’s and y’s is there for smarties to find.

@ph1 @patricioe @SplitSoftware Security is a *fun* topic. Split.io is architected to never send PII out of a client SDK to the cloud for evaluation, which means we never see it, let alone decide whether to store it.

Flag evaluations are actually fast. And yes, client side evaluation works. I'm sorry to call you out publicly @ph1 but none of us agree on what you wrote here: docs.openfeature.dev/blog/catering-… Why are client side evaluation slow when things can be evaluated locally? @SplitSoftware

@ph1 @patricioe @SplitSoftware When evaluation is done at the very moment the user reaches the flagged code, records of *that* evaluation are meaningful. That’s not the case with evaluations done and cached at launch.

A feature flag is more than a toggle ON/OFF 💪🏻 Advanced feature flagging tips: 1. Optimize Gradual Rollouts 2. Bring Control to Random Sampling 3. Achieve Comparative Analysis 4. Hash Your Randomizations split.io/blog/advanced-… @davekarow #featureflags #featuretoggle #devops

@RaulJuncoV @SplitSoftware Finally, since you'll find a lot of talk about using data to make sense of what's happening with your flags, this security primer that shows how we pull that off without storing PII on our end might come in handy. split.io/wp-content/upl…

@RaulJuncoV @SplitSoftware You can also get a quick sense of how we organize our approach by checking out the Essential Guides and Step by Step sections in Learning about Split here: help.split.io/hc/en-us/categ…

90% of developers think that Feature Flags are just for hiding functionality, and they are wrong. Feature Flags is a powerful solution to decouple your Deployments from your Releases. 5 facts about Feature Flags you need to know to take full advantage of them.