News for hackers. Stuff that matters.
Re:Lines of code that will beat A/B testing every time (2012) by zeroCalories on Monday January 13, 2025 @10:59PM (#42693439)
What do you think of using the epsilon-first approach then? We could explore for that fixed time horizon, then start choosing greedy after that. I feel like the only downside is that adding new arms becomes more complicated.
Re:Lines of code that will beat A/B testing every time (2012) by hinkley on Tuesday January 14, 2025 @01:27PM (#42701551)
What percent of companies using A/B testing do you think know what the Texas Sharpshooter is and how to identify it, let alone what epsilon is or what it means?