One of the things that sets a good programmer apart is the willingness to fearlessly dig into someone else's code. I've heard it said before that you're responsible for every line of code you ship to your users. It follows that you shouldn't treat your dependencies as black boxes. Getting a stack trace that's 3 or 4 levels deep in Django/React/<insert library here>? Dig under the covers and understand what's happening. Include that information in a bug report, and better yet, open a PR offering to fix it.
You'll learn a whole lot and be more effective if you let your curiosity expand beyond code you/your team has written.
You'll learn a whole lot and be more effective if you let your curiosity expand beyond code you/your team has written.