So for raw performance, I still favor the iterative solution. But for a well-balanced approach that is lighter on RAM but trivially different in x-time, I agree the generator is best.
Yeah, that's usually it. The advantage with the generator is that you can pause it and resume it. They are basically a simplified version of continuation passing style.
Both interviewers chuckled along with me though and told me that they had done the same exact thing I did the week before when they had first seen that problem in preparation for my interview.
That's cool. If they saw that, it means they empathize and recognized that you were working towards a solution
Either way, I had a blast, loved the people and the interviewers, and am really hoping things work out.
Well, that's really important. Sometimes we go into interviews hoping the company will like us but forgetting that we have to like them as well :D
Crossing fingers, especially now that your skills are in demand!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, that's usually it. The advantage with the generator is that you can pause it and resume it. They are basically a simplified version of continuation passing style.
That's cool. If they saw that, it means they empathize and recognized that you were working towards a solution
Well, that's really important. Sometimes we go into interviews hoping the company will like us but forgetting that we have to like them as well :D
Crossing fingers, especially now that your skills are in demand!