I have to re-read how to do lambdas more often than I care to try and remember. Every time I do, I ask myself why I'm doing it.
If you are one of the cogniscenti who don't suffer this cognitive burden please treat the rest of us kindly.
"oh, you mean you can't read music: how funny I can hear the entire orchestra"
Sometimes however, there will be a recursion, which dumbfounds me as well :) I still feel I improve though. Just the other day I came up with a pair of mutual recursive functions, as if it was nothing, to solve a specific problem, by splitting it into 2 subproblems (or maybe 2 states in an automaton).
Often there is a very clear idea behind a recursion, that, once one has heard it, becomes completely obvious. Maybe not always.
About ZIP: Imagine you wanted to work on 2-tuples made out of pairs of elements from 2 lists. That's what ZIP does. Maybe also works for more than 2 lists, I don't know.
But the moment I start seeing mutation, or for loops complex than a for each over a data structure (like nested ones, or while, or weird indexing) my brain completely shuts down. In my first professional job (F# developer) I had to look up how to write classes every time we created one (not often, to be fair).
I think it's all a matter of habit and familiarity, although I'll admit that finding places that program functionally (where I'm most proficient) is really hard