News for hackers. Stuff that matters.

A comment on 20 lines of code that beat A/B testing (2012). Parent comment

Re:20 lines of code that beat A/B testing (2012) by chii on Wednesday April 06, 2016 @05:45AM (#11437719)
And it turns out you randomly assigned B to a poorer user more often than not, and this make B worse...
[ Parent | on HN ]
Re:20 lines of code that beat A/B testing (2012) by eru on Wednesday April 06, 2016 @06:12AM (#11437801)
That's why you do it properly randomized. Statistics tell you how much of a risk of your scenario (and similar) you are running at most.
[ Parent | on HN ]