Dave Karow

Build software faster without breaking things. Test what works (user behavior vs your opinion). Advocate for Feature Flags and Experimentation @SplitSoftware

[Dave Karow @davekarow]

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: https://t.co/XW0x4bIHqd

[Dave Karow @davekarow]

@mipsytipsy @monkchips Two years after coining the term, @monkchips summed up the echos of the idea here: https://t.co/byb6Cdx0K7

[Dave Karow @davekarow]

@jeremydavis @housecor @SplitSoftware Here’s the link to doc page for Rollout Board for anyone following along. https://t.co/rYzFkAe2Pv

[Dave Karow @davekarow]

@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 🤷‍♂️

[Dave Karow @davekarow]

Interview with @davefarley77 is https://t.co/5NMGzi7lzN and the Progressive Delivery talk I gave is https://t.co/H3E76wZh4R

[Dave Karow @davekarow]

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.

[Dave Karow @davekarow]

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

[Dave Karow @davekarow]

@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.

[Dave Karow @davekarow]

@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 :-)

[Dave Karow @davekarow]

@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.

[Developer Avocados 🥑 @DevRelAvocados]

🥑New Avocados Weekly is out - https://t.co/uF2HpdjLL1

📝Content from @rosegoldlining, @remotesynth, @andypiper, @janackeh, @blackgirlbytes, @saltnburnem, @wesley83, @jasonhand, @daedtech, @kamranayub, @SlashDataHQ & @gemanor

📚CFPs from @infobipshift, @pyconlt & @BeerCityCode

[Dave Karow @davekarow]

@sesteva @patricioe @ph1 @SplitSoftware The motherlode of SDK docs, including both client and server SDKs, examples, and more, starts here: https://t.co/vgmne3V3s5

[Dave Karow @davekarow]

@sesteva @patricioe @ph1 @SplitSoftware 2/2: For example here is that section from JavaScript SDK docs: https://t.co/36LliB0Ne4
- Using the SDK
--Basic use
--Shutdown
--Multiple evaluations at once
--Attribute syntax
--Binding attributes to the client
--Get Treatments with Configurations

[Dave Karow @davekarow]

@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.

[Dave Karow @davekarow]

@ph1 @patricioe @SplitSoftware Security is a *fun* topic. https://t.co/fmpylx5Pr0 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.

[Dave Karow @davekarow]

@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.

[Split @SplitSoftware]

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

https://t.co/OXEHRyReR7

@davekarow

#featureflags #featuretoggle #devops

[Dave Karow @davekarow]

@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. https://t.co/akeEm6tXtO

[Dave Karow @davekarow]

@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: https://t.co/RwuGkqyj24