I'm not a traditional programmer, but I'm learning Python mainly for text processing and XML handling. I've heard different opinions on whether it's necessary to read all the language's documentation to truly understand it. Some resources, like 'Learn Python the Hard Way,' suggest that you should, but I find the documentation detailed and often overwhelming. I've been told to start with the reference manuals, but even those are tough to get through. Since I also have ADHD, I'm looking for better ways to approach reading the docs. Any tips or strategies to make this process easier or more engaging would be really appreciated!
5 Answers
When learning something new, like the rims and tires on a car, you don't need to know every detail, just the relevant parts. I've been learning for a little while, and I find that starting with a high-level view and then filling in the gaps as I get more specific is really effective. Break down what you want to achieve and then look for the information that directly supports that. Just remember, finding the right info takes time, but it’s worth it!
I think you should definitely read the parts that are relevant to what you're currently working on. Each programming language has its quirks, and the documentation is where you often find those pitfalls explained. But don’t worry about reading every single detail—focus on what you need at the moment, and slowly expand your knowledge as you work on different projects. To make docs less overwhelming, I tend to read them at a surface level first and then dive deeper into specifics when a challenge comes up.
That workflow with the IDE sounds smart, I’ll definitely try that!
It's important to understand the essence of your goals. You're learning Python for text processing and XML handling, not to master every aspect of the language. A fundamental grasp of Python and knowing where to find information (like API docs for specific libraries) can make your coding much easier. Don't overload yourself; focus on the tools and techniques that help you accomplish your tasks.
Thanks for the detailed breakdown and tool suggestions!
Definitely not! Trying to read all the documentation would be a monumental task—it's just too much. Personally, I usually Google what I need when I'm coding, which leads me straight to helpful snippets or library functions. That's how I tackle my programming tasks, with the exception of when I needed to learn assembly language, where I memorized the instructions out of necessity.
Thanks for the insight!
It's like asking if you need to read every dictionary entry to fully understand a language. Sure, knowing everything would be great, but it’s not practical. Most people learn by doing and using, not just by reading. Use the docs to look up things you forget or to dive deeper occasionally when you need to solve new problems. Don’t feel pressured to read everything because nobody does that!
You make a good point, thanks!
I can relate! It’s definitely confusing with poorly written docs.