Comments by "yapdog" (@yapdog) on "STOP LEARNING LANGUAGES | Prime Reacts" video.

@simonfarre4907 Iteration should be used wherever possible, but recursion can't be escaped in some situations where you need to see how a series of values change per-call. You could simulate it with your own stack on non-branching recursion, but if you have multiple branches of recursion (as I do) where functions call other functions that may loop back and/or to other looping functions which may or may not loop back or elsewhere and so on, you'll quickly see the value of just using recursion.
2
It all depends on what you're developing. Some things require a greater context to see the problem. For example, I've been developing a platform for developing languages. The problems that arise simply cannot be easily identified by using a debugger, especially since much of it is multibranch recursion hell. I have to actually print out the construct hierarchy with named enums and such.
1
Honestly? I tend to find it very difficult to read other peoples' code, too. More often than not, when I'm seeing something that doesn't make sense I tend to doubt my own self. But then when I look deeper, I sometimes see that the code is not well written... IMHO. For example, I recently experienced this with regex engines. I had to chuck everything I found--even in popular open source release code--and just start from scratch, ignoring everything else. It was a coding slog, but it was faster and less painful than banging my head against the wall until the nonsensical made sense.
1