I jump into a new language, a new technology, and immerse myself in it. Ask Qs on SO, read books, but write code. This is how I taught myself how to code when I

I jump into a new language, a new technology, and immerse myself in it. Ask Qs on SO, read books, but write code. This is how I taught myself how to code when I was a teen, and it's been very effective ever since, as I have moved from teen to undergrad to grad student to professional. Solo self-education via practice, supplemented by voracious reading. I would quantify a key difference between an effective intern and an ineffective intern as "has this person written 10KLoC". Writing software is a craft, and crafts require practice. After initial competence is achieved, i.e., you can do your first coding language/tech and be comfortable, you need to choose another, different, one and repeat the process. It will break individual understandings of that one system and show you commonalities. Then, do it again. Even more different. Rinse, repeat. The breakthrough and toughness are required for getting better. At a certain point, the problem of "learning how to code" or "getting better at coding" disappears and you need to understand how to work with others and building work products for them - open source or otherwise. On and on it goes.