Let's explore these two approaches together.
You: The first approach is to learn how to use the library effectively without diving into the source code. You’d focus on mastering the API, understanding how to combine functions and classes, and getting your web app up and running quickly. The goal is to have a working product as soon as possible. What’s wrong with that?
Me: Nothing inherently wrong, but let’s think about what you might miss out on. By not understanding the source code, you’re relying entirely on the documentation and examples. What happens if you hit a limitation or a bug in the library? How would you troubleshoot or extend the library to meet your needs if you don’t understand its inner workings?
You: That’s a valid point, but in practice, I can get a lot done without needing to understand the source code. If I hit a limitation, I could always look into the source code then or even seek help from the community or maintainers. Why should I spend time understanding the entire code