20 lines of code that beat A/B testing every time

Re:20 lines of code that beat A/B testing every time by 51Cards on Tuesday May 29, 2012 @10:21PM (#4041036)

re: #3... you can also remove items at will. If you look at the counters and find option C is consistently the lowest performer, then you can remove it from the code and remove the counter. It doesn't mean cruft needs to pile up.

[ Parent | on HN ]

Re:20 lines of code that beat A/B testing every time by btilly on Wednesday May 30, 2012 @12:50AM (#4041430)

But how do you know when you can do that? Particularly with the slower convergence issue, and the potential presence of confounding factors like #2?

[ Parent | on HN ]