On the other hand, the current interviewing trend generates a steady supply of nifty, bite-sized problems to solve for fun. I keep a "practice" repo on Github,

On the other hand, the current interviewing trend generates a steady supply of nifty, bite-sized problems to solve for fun. I keep a "practice" repo on Github, where I put my solutions. Often, for an extra challenge, I'll prove the solutions correct or try to write clear explanations of how to solve the problems from scratch. (Proving something helps me to see the hidden structure upon which my intuition rests. Explaining something helps me to lock it in my head.) Over the years, I have learned a lot from this practice and have built up a repo that serves to keep my memory fresh. Here are some fun examples: https://github.com/tmoertel/practice/blob/master/dailycodingproblem_com/find_non_triplicate_int.py https://github.com/tmoertel/practice/blob/master/dailycoding... https://github.com/tmoertel/practice/blob/master/dailycodingproblem_com/first_missing_positive_integer.py https://github.com/tmoertel/practice/blob/master/dailycoding... https://github.com/tmoertel/practice/blob/master/water-holding-capacity/water_holding_capacity.py https://github.com/tmoertel/practice/blob/master/water-holdi... So, in at least one respect, I like the obsession with interview problems :)