Live data from Hacker News

The Explore vs. Exploit Dilemma

nathanzhao.cc

11–16 of 16 posts

Re: The Explore vs. Exploit Dilemma

#12

A simplified heuristic[0] for this for those interested in personal applications: it works out that you should exploit the best opportunity you come across once you’ve explored about 37% of the search space. [0]: https://en.m.wikipedia.org/wiki/Secretary_problem

Note that it is if you only want the best candidate, all others being equally bad. If, instead, you are content with just a "good" candidate to avoid having to pick a terrible one, then a proposed solution is for the cutoff to be sqrt(n), where n is the number of candidates.

See "Cardinal payoff variant" in the Wikipedia page.

Re: The Explore vs. Exploit Dilemma

#13

A simplified heuristic[0] for this for those interested in personal applications: it works out that you should exploit the best opportunity you come across once you’ve explored about 37% of the search space. [0]: https://en.m.wikipedia.org/wiki/Secretary_problem

With the caveat that this number is for situations where you cannot backtrack (choose a previously seen option that isn’t the current one). There is a great book Algorithms to Live by that goes over this explore/exploit problem and more. I recommend it.

I second that recommendation. There's some really good discussion on when and how to apply heuristics like this to real-life decisions.

Re: The Explore vs. Exploit Dilemma

#14
post #4

Thanks for writing, a problem I struggle with. I think confidence in oneself impacts the decision. You seem to be highly employable, meaning you can err on the side of exploration. I’m less convinced about that for myself, which makes me anxious to keep exploring. Although I find it very difficult to resist that part of my nature!

I personally think that if you aren't employable you should probably try to explore more to find a good arm to begin to exploit (supposing you are young with long-range T and are able to take advantage of learning opportunities once given them). There's usually a lot of variance in life's arms, so it's good to try as long as exploring doesn't ruin your other possibilities (or you have other responsibilities). Otherwise, you would be stuck exploiting an overall not-so-beneficial arm.

Re: The Explore vs. Exploit Dilemma

#15
post #3

See also Thompson sampling[+] for a different approach to multi-armed bandits that doesn't depend on explicitly distinguishing between explore-exploit. [+] https://en.wikipedia.org/wiki/Thompson_sampling

I've read about this -- decided not to include in the blog because wasn't very easy to analogize to the problem in an especially unique way. Still interesting though!

Re: The Explore vs. Exploit Dilemma

#16
post #5

I've been using evolutionary techniques with Pareto front optimization to deal with this tradeoff. If two (or more) objectives are in direct conflict, but otherwise don't dominate one another, we simply take them all. Then, the problem becomes one of making sure you have enough resources to maintain the frontier across the generations. If you do have to collapse the frontier, you can use things like crowding score to…

I think the way life frames many of its problems forces you to simply run into the jungle, cutting through the shrubbery. At least in the sense of deeply technical projects, it's difficult to utilize a Pareto front optimization system, as learning something fully requires long stretches of complete focus. You lose a lot of cached information if you're always switching between contexts. So, I guess it depends on the type of end goal you hope to achieve, but I personally wouldn't utilize Pareto front optimization (maybe I only think this because I am relatively deep into exploitation though).
Post reply on HN