There is a long-standing school of computer programmers who learn to code (not algorithms, not group communication, not conveying intention clearly, but the mechanical "coding" parts) from reading manuals and practicing with projects (real or "learning" or both). I'm from that school myself. People from this school tend (large generalization admitted) to learn a small core from a tutorial, and then glean the rest of the practice of coding (often, "how to use libraries") by reading manuals (a large part of the unix `man' tradition, for example).
There is also a very large group of professional, prolific programmers who learn coding through interactive exploration of APIs. This isn't just limited to interpreted vs. compiled languages (although I believed that it comes in part from the rise of teaching via interpreted languages); it also comes out of the practice of learning via auto-complete and live documentation. It also has roots in the rise of problem solving via searching on google/stack exchange/etc.
I hope that helps,