On the other hand, I will say that even as an English-speaker, I find myself recently skipping the "human language" explanation and jumping directly to the code when I read results from Google etc. I think this is probably the best strategy for anyone not adept at English: start from the code, and then when you don't understand something, go back to the explanation above/below it.
Yes but it doesn't help with thing not directly code related, environmental stuff etc... Which is usually the stuff I end up googling come to think of it.
Plus to dive into the code you have to have a reasonable idea where to start to look for your problem which can also be a barrier in a complicated project where the comments / guides / documentation is in English.
