<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ab-Testing on Ryan Orban</title><link>https://ryanorban.com/categories/ab-testing/</link><description>Recent content in Ab-Testing on Ryan Orban</description><generator>Hugo</generator><language>en-us</language><managingEditor>me@ryanorban.com (Ryan Orban)</managingEditor><webMaster>me@ryanorban.com (Ryan Orban)</webMaster><copyright>Ryan Orban</copyright><lastBuildDate>Mon, 29 Sep 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://ryanorban.com/categories/ab-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>How Optimizely (Almost) Got Me Fired</title><link>https://ryanorban.com/notes/optimizely-ab-testing/</link><pubDate>Mon, 29 Sep 2014 00:00:00 +0000</pubDate><author>me@ryanorban.com (Ryan Orban)</author><guid>https://ryanorban.com/notes/optimizely-ab-testing/</guid><description>&lt;h3 id="summary" class="scroll-mt-8 group"&gt;
 Summary
 
 &lt;a href="#summary"
 class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block"
 aria-hidden="true" title="Link to this heading" tabindex="-1"&gt;
 &lt;svg
 xmlns="http://www.w3.org/2000/svg"
 width="16"
 height="16"
 fill="none"
 stroke="currentColor"
 stroke-linecap="round"
 stroke-linejoin="round"
 stroke-width="2"
 class="lucide lucide-link w-4 h-4 block"
 viewBox="0 0 24 24"
&gt;
 &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /&gt;
 &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /&gt;
&lt;/svg&gt;

 &lt;/a&gt;
 
&lt;/h3&gt;
&lt;p&gt;This SumAll blog post became one of the most-cited criticisms of naive A/B testing tools when it was published. The author ran experiments through Optimizely, declared winners based on the platform&amp;rsquo;s significance indicators, shipped changes — and later discovered the winning variants were not actually better. The culprit: &lt;strong&gt;optional stopping&lt;/strong&gt;, also called the peeking problem.&lt;/p&gt;</description></item><item><title>Fun with Stats: How Big of a Sample Size Do I Need?</title><link>https://ryanorban.com/notes/fun-with-stats-sample-size/</link><pubDate>Sat, 12 Jul 2014 00:00:00 +0000</pubDate><author>me@ryanorban.com (Ryan Orban)</author><guid>https://ryanorban.com/notes/fun-with-stats-sample-size/</guid><description>&lt;h3 id="summary" class="scroll-mt-8 group"&gt;
 Summary
 
 &lt;a href="#summary"
 class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block"
 aria-hidden="true" title="Link to this heading" tabindex="-1"&gt;
 &lt;svg
 xmlns="http://www.w3.org/2000/svg"
 width="16"
 height="16"
 fill="none"
 stroke="currentColor"
 stroke-linecap="round"
 stroke-linejoin="round"
 stroke-width="2"
 class="lucide lucide-link w-4 h-4 block"
 viewBox="0 0 24 24"
&gt;
 &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /&gt;
 &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /&gt;
&lt;/svg&gt;

 &lt;/a&gt;
 
&lt;/h3&gt;
&lt;p&gt;Julia Evans writes characteristically direct posts about technical concepts, and this one tackles sample size calculation for statistical hypothesis testing. The core question she answers is practical: if I want to detect a 5% improvement in my metric, how many users do I need in my experiment? The answer requires understanding statistical power — the probability that your test will detect a real effect if one exists.&lt;/p&gt;</description></item><item><title>So You Think You Can Test?</title><link>https://ryanorban.com/notes/so-you-think-you-can-test/</link><pubDate>Wed, 02 Jul 2014 00:00:00 +0000</pubDate><author>me@ryanorban.com (Ryan Orban)</author><guid>https://ryanorban.com/notes/so-you-think-you-can-test/</guid><description>&lt;h3 id="summary" class="scroll-mt-8 group"&gt;
 Summary
 
 &lt;a href="#summary"
 class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block"
 aria-hidden="true" title="Link to this heading" tabindex="-1"&gt;
 &lt;svg
 xmlns="http://www.w3.org/2000/svg"
 width="16"
 height="16"
 fill="none"
 stroke="currentColor"
 stroke-linecap="round"
 stroke-linejoin="round"
 stroke-width="2"
 class="lucide lucide-link w-4 h-4 block"
 viewBox="0 0 24 24"
&gt;
 &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /&gt;
 &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /&gt;
&lt;/svg&gt;

 &lt;/a&gt;
 
&lt;/h3&gt;
&lt;p&gt;Lukas Vermeer&amp;rsquo;s hackathon project is a deceptively simple interactive quiz: you&amp;rsquo;re shown a series of test results and asked to judge whether each shows a real effect (A/B test) or no effect (A/A test). The exercise is humbling — human intuition for statistical patterns is poor, and most people perform near chance. It&amp;rsquo;s a visceral demonstration of why A/B testing requires statistical significance testing rather than visual inspection.&lt;/p&gt;</description></item><item><title>Pelican + PlanOut: A/B Testing on a Static Site</title><link>https://ryanorban.com/notes/pelican-planout-ab-testing/</link><pubDate>Tue, 27 May 2014 00:00:00 +0000</pubDate><author>me@ryanorban.com (Ryan Orban)</author><guid>https://ryanorban.com/notes/pelican-planout-ab-testing/</guid><description>&lt;h3 id="summary" class="scroll-mt-8 group"&gt;
 Summary
 
 &lt;a href="#summary"
 class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block"
 aria-hidden="true" title="Link to this heading" tabindex="-1"&gt;
 &lt;svg
 xmlns="http://www.w3.org/2000/svg"
 width="16"
 height="16"
 fill="none"
 stroke="currentColor"
 stroke-linecap="round"
 stroke-linejoin="round"
 stroke-width="2"
 class="lucide lucide-link w-4 h-4 block"
 viewBox="0 0 24 24"
&gt;
 &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /&gt;
 &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /&gt;
&lt;/svg&gt;

 &lt;/a&gt;
 
&lt;/h3&gt;
&lt;p&gt;Trent Hauck&amp;rsquo;s post demonstrates how to integrate PlanOut — Facebook&amp;rsquo;s experiment framework — with Pelican, a Python-based static site generator. The combination is technically interesting: static sites don&amp;rsquo;t have server-side request handling, so running A/B tests normally requires either a CDN with edge logic or client-side assignment. This post works around the limitation by having PlanOut generate the variant assignments at build time.&lt;/p&gt;</description></item><item><title>Statistical Formulas for Programmers</title><link>https://ryanorban.com/notes/statistical-formulas-for-programmers/</link><pubDate>Mon, 20 May 2013 00:00:00 +0000</pubDate><author>me@ryanorban.com (Ryan Orban)</author><guid>https://ryanorban.com/notes/statistical-formulas-for-programmers/</guid><description>&lt;h3 id="summary" class="scroll-mt-8 group"&gt;
 Summary
 
 &lt;a href="#summary"
 class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block"
 aria-hidden="true" title="Link to this heading" tabindex="-1"&gt;
 &lt;svg
 xmlns="http://www.w3.org/2000/svg"
 width="16"
 height="16"
 fill="none"
 stroke="currentColor"
 stroke-linecap="round"
 stroke-linejoin="round"
 stroke-width="2"
 class="lucide lucide-link w-4 h-4 block"
 viewBox="0 0 24 24"
&gt;
 &lt;path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /&gt;
 &lt;path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /&gt;
&lt;/svg&gt;

 &lt;/a&gt;
 
&lt;/h3&gt;
&lt;p&gt;Evan Miller wrote a post translating the most commonly needed statistics formulas into programmer-friendly notation — avoiding the Greek letter soup of academic statistics textbooks and presenting formulas in a way that maps to implementation. The target audience: software engineers who need to implement A/B testing, analyze experiment results, or build product analytics without a statistics background.&lt;/p&gt;</description></item></channel></rss>