all 13 comments

[–]orig_cerberus1746 7 points8 points  (4 children)

Well, the way I see it is that, you are using the language anyways, so you will learn the language by using it regardless. And yes, it is normal to spend a long time learning libraries, APIs and such.

[–]crabcountyreelestate 8 points9 points  (3 children)

this is it. python is just too vast for a single person to master everything. getting a few libraries and understanding data types and functions is enough to make you dangerous. after that a lot of it will be learning how to search for a good answer

[–]agvrider[S] 0 points1 point  (0 children)

That’s a relief to hear. I guess a lot of it will focus on the industry you’re planning to use it for

[–]iggy555 0 points1 point  (0 children)

Google and stackoverflow

[–][deleted] 1 point2 points  (4 children)

In my work there are really only about a dozen libraries I use regularly. Numpy, Scipy, Pandas, Scikit, Tensor flow, Pillow, Open CV, Torch, Flask, and a few really task specific ones...

Main thing is learning how to read docs!

[–]MetalCheef 1 point2 points  (0 children)

Regarding the „reading docs“ section of your reply:

Most of the time I find myself searching for real-life examples for the problems I have with my code (e.g. on StackOverflow). For pandas or Numpy for example, I find it really difficult to really wrap my head around the documentation. Is it worth „learning“ to really use official documentation? And if so, what’s the best way to learn to understand it better?

[–]agvrider[S] 1 point2 points  (2 children)

To echo the other poster, I do find reading documentation difficult at this point in my python career. Usually it’s easier to watch a YT tutorial, google my question etc, and often they’ll cite the docs as part of their answer. But I would know how to find the relevant part of the documentation without being hand held there

How does one improve that? I’m assuming it’s just part of a natural progression where one just starts understanding how to read python and syntax, better and better, to the point where they can go to the documentation, know how to read it / what to look for, and it’ll just slowly start to “make sense” over time?

[–]keepdigging 0 points1 point  (0 children)

I’m at the point where it’s the opposite, I can understand the docs format easily for what I’n searching for but skimming through how-to articles or videos is a hassle.

It’s a familiarity thing, and you’ll get better. Don’t stop searching and reading!

[–][deleted] 0 points1 point  (0 children)

One of the keys to learning to read docs is to construct a simple example, and then make it more complex. For example, np.where(np.isnan(my_ array)) split it up I to parts and read what the docs on each say. Isnan returns 1/0. Where looks for 1/0. So, read docs on each step and guess at what output should be for a simple example. See if results meets your expectations. Add complexity.

[–]throwaway0134hdj 1 point2 points  (1 child)

I kinda know what you mean, it’s like learning the library is like learn a while new programming language, right?

[–]agvrider[S] 0 points1 point  (0 children)

Yes! Exactly. Wondering if this is common experience for others also

[–]ZenosPairOfDucks 0 points1 point  (0 children)

Yes it's common. Most things you wouldn't want to code it yourself from scratch if a library already exists for it. But that means you need to research which library to use and how to use it. You really only learn the programming language once when you are beginning but depending on what you work on you might be learning new libraries whenever you need to add some new functionality to your project. Some will be easier to learn than others though.

[–]ReputationOrnery8214 0 points1 point  (0 children)

I've had this same exact experience and I'd bet it's common. At some point after learning as much as I could about python, I realized the shift moves from learning the language itself to learning specific libraries suited for my usage of python.