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.
[ Parent
| on HN ]