Learn why things work, not just how to make something work. You'll probably have plenty of times where you know that "if I write this line of code, this thing

Learn why things work, not just how to make something work. You'll probably have plenty of times where you know that "if I write this line of code, this thing happens, and that solves the problem". Dig into exactly what that is doing and understand why it works as it does. A lot of the time this just means reading all the documentation (not just the 1-liner you can copy/paste and move along) and source code of libraries. A good exercise you can do is to open up some code (ask a coworker for a good place to start), look at it line-by-line, and ask yourself if you know exactly what is happening on each line. You probably won't know and that's your trigger to go read up on something. From there you'll have great questions that a coworker should be happy to talk about with you. In my experience, new developers that take this approach of truly learning (rather than just making things work) grow fast and impress the team.