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 darkxanthos on Wednesday April 06, 2016 @07:22AM (#11438003)
My professional advice to people who make these unmeasurable changes is: Then don't do them. The worst part about unmeasurable changes is you can't verify if it has a negative effect either and you're essentially saying "I'm focusing on making this change when it will have negligible impact on the business."

You have better things to do.

[ Parent | on HN ]
Re:20 lines of code that beat A/B testing (2012) by spiderfarmer on Wednesday April 06, 2016 @07:54AM (#11438117)
I agree, every article about A/B testing is talking about making small changes and measure them, while you should be measuring only big changes or nothing at all.
[ Parent | on HN ]