When I work with graduates, I often encourage them to try and understand "1 level down" - that is to say, understand the general design philosophy and how to navigate the tools and libraries you are using. That gives you a better understanding for how to use them, whilst also allowing you to side step the documentation when you need to. On the other hand, if you try to understand what the atoms are doing on the silicon when you run an SQL command, you might be a tad overwhelmed...
