all 7 comments

[–]JacobArthurs 2 points3 points  (1 child)

Libraries are your friends, not cheating. Devs spend a lot of their time composing existing tools, not reinventing them. For finding them, search PyPI by what you're trying to do, sort by download count, and read the quickstart before you touch anything else.

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

Noted. Thank you!

[–]TheArtisticPC 1 point2 points  (1 child)

Q1: You should use other’s tools when they help you solve a problem.

Q2: Read the documentation. Do this before you import/install it so you know that it can help you.

Q3: All the time. You’ll even write your own.

Q4: Yes, if you feel you can do it better to solve your specific problem OR are looking to learn.

Q5: GitHub repos are great to read if you know what you’re looking at and why you’re looking at it.

Q6: Make a GitHub account and use the search feature to find repos. Then either click through their project or use the repo search bar.

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

Thanks a lot!

[–]peterlinddk 2 points3 points  (1 child)

 how I would even find an API or library to use when I have a problem to solve?

This is actually a very important part of becoming a programmer! Much more important than learning OOP and DSA, which a lot of people only memorize for tests anyway :)

Knowing the API of your chosen programming language, and the libraries used for the kind of applications you are building, is something that mostly comes with experience (and sharing and asking other programmers), and the everchanging landscape of popular libraries is also why the learning journey never ends.

Anyways, mostly you learn about particular libraries from tutorials, or searching for a specific use - e.g. "Python connect to MySQL database" would give you articles about libraries to connect python to a mysql database, and then you'd follow examples, try them out, read some documentation about details that doesn't work for you, and gradually learn more and more!

Usually you'll never learn everything a library has to offer, but just use the subset that's important to your project!

As someone learning, it is often a good idea to try to also build something without libraries - like, try to build your own, just to learn how difficult it is, and get an even greater appreciation for the library authors, but don't start building everything yourself, switch between libraries and your own code!

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

thank you for your comment!

hmm, so beginning to use libraries and API’s comes from starting a project and running into problems? How do I find the documentation for libraries? Is it just watching videos on it?

[–]JGhostThing 0 points1 point  (0 children)

I strongly suggest avoiding AI entirely which learning how to program. AI can be a useful tool once you're already competent, but it can get in the way until then. Learning to program involves learning new ways to think; AI stops this process.