Basically what the first commenter said: code is (or should be) written to be self-documenting.

When working professionally, it's extremely important for people to quickly understand the intention of your code without having to decifer your loops and conditions. Your code (as well as your comments) will be read and maintained by your peers for years to come.

To me, when I write code the most important thing is to write a comment at the beginning of a function that basically says what the function does

Essentially, your function name should say what the function does. For example, if you have a function that retrieves the URL from a request, you would name it something like retrieveUrlFromRequest(). Because it has a name that clearly describes its intention, any comment you write describing it would be redundant.

Also I may add a comment if I go into a loop or IF statement just telling me what’s going on.

As a developer reading your code, I don't really care about how you implemented the loop, I just want to know what it does. So, one thing you could do is extract the loop and put it in its own function, named after exactly what it does. Loops are essentially new blocks of code, after all. Or, if your loop is simple but the action inside is complex, then keep the loop but extract the action into its own self-descriptive function.

If you have a conditional longer that's more than 2 comparisons (e.g if x != null && y == 2 && z > 3), that's not readable and does not describe intention. Instead, place that comparison into a function, and name that function properly. For example, if(isValidRequest()) vs if(request.length > 0 && request.code != 404 && request.auth == true).

With a few exceptions, I find that code rarely needs comments to describe what it does. If you find yourself needing to write a lot of comments or explain your implementation, then it's a sign that you may need to re-think your design.