I think it’s good advice generally speaking, but it won’t work for beginners. Studying great code is a great way to go from intermediate to expert, but if you haven’t already gone from beginner to intermediate than you probably won’t be able to recognize what is good code or understand why it is good.
Immersion work well for beginner language learning because natural languages are fine with loose, sloppy, full of errors mishmash. The point is to get going and fix all problems later. I don’t think this would work well with programming languages.
This seems pretty similar to the “search for what you want on StackExchange / GitHub and copy/paste” approach to learning to code, which appears to work fairly well.
I think it’s good advice generally speaking, but it won’t work for beginners. Studying great code is a great way to go from intermediate to expert, but if you haven’t already gone from beginner to intermediate than you probably won’t be able to recognize what is good code or understand why it is good.
I wonder. Immersion works pretty well for beginner language learning. It might be more effective than you think for computer software.
Immersion work well for beginner language learning because natural languages are fine with loose, sloppy, full of errors mishmash. The point is to get going and fix all problems later. I don’t think this would work well with programming languages.
This seems pretty similar to the “search for what you want on StackExchange / GitHub and copy/paste” approach to learning to code, which appears to work fairly well.
I suspect it works well for picking up a new language when you already know how to code. I doubt this is a good method for beginners in programming.