I'm curious about how people approach reading documentation when learning a programming language. Do you dive straight into the official docs for syntax, functions, and libraries, or do you prefer to experiment with coding on your own first? Maybe you find articles or YouTube tutorials more helpful? Everyone has their own learning style, and I'd love to hear what works best for you!
4 Answers
Official documentation is always my starting point. It provides accurate and up-to-date information, which is essential. Blogs and articles can be hit or miss—sometimes I find a gem, but often they're not reliable.
I usually try to solve things on my own for a bit first, but if I'm stuck, the documentation is my go-to. It’s there to help! I find that if I can’t figure something out from the docs, I probably need to step back and learn more about what I'm working with.
For embedded systems, though, reading the docs is crucial. Learning how to connect things often requires that foundational knowledge.
I like to mix things up! I read the documentation while experimenting with code. It’s super helpful to see how the official guides explain things, especially since they're usually written by the creators. I generally avoid video tutorials due to worries about outdated info.
I keep the documentation open in a tab while coding. If I forget the syntax or need help with a function's arguments, I just flip back and check. Sometimes, I also use Google for quick fixes or examples.
That makes sense! As a beginner, I think I might rely too much on tutorials instead of checking docs first. I'll definitely consider switching it up as I get more experienced.