porfirion
Of course I understood the concept of doing something x times with increasing counter, but I couldn't see the clear relation between what I wrote and what it did. It seemed a bit magic and I wanted to "truly understand" it before mapping the concept to syntax. It seemed too arbitrary to me to rely in my thinking on such magic.
My strategy was to unloop every loop I saw. It was ridiculous, I didn't have enough resources to keep even smaller loops in mind and I quickly forgot them. After few days I just gave up and committed it to my memory. Only then I felt that I truly understand.
I think I tried programming skipping this step but I just got irritated and really unsure if what I'm doing makes any sense. I remember it being the same with recursion, except a bit more mind-boggling. Now every time I try to understand something similar I try to reduce it to simplest case and just commit it.
I suppose other people may be unaware of what is actually keeping them from understanding and never get that far.
Expanding on this: I don't listen to music while programming. If it can be treated as background music, then it's too boring to hold my attention when I need to get distracted for a moment. I try to listen to some challenging music before programming to get focused, and it seems to be working.