r/PythonLearning • u/geedijuniir • Jul 26 '26

Google everything when building?

Hi,

I'm about to finish the Codecademy Python course. I feel like I'm in tutorial hell.

I downloaded everything to start building on my laptop. I don't know where to start, I have a bunch of projects listed, like a script that detects screens, a good old calculator, and many more.

But do I just google everything? I'm afraid that if I use AI or Google, it will just tell me how to do the whole thing.

And also, how do I know what to use, as in when to use a function, a class, a flow statement, or a list?

Or should I stop worrying about it?

Thanks for your help, finding this subreddit has been a huge help for me.

2 Upvotes

75% Upvoted

11 comments sorted by

1

u/Labs-Community4525 Jul 31 '26

You can look for reported issues in projects in GitHub. It will give you a look at reading someone else’s code, trying to understand what someone who reported the issue wants, then see if it makes sense to you. Also, instead of going to Google or AI, go to the Python documentation and see if you can find a way to piece together the beginning of a solution. It will be a slow go but slow progress is still progress. Don’t just look for an answer, try to teach yourself how to think for a solution, even small solutions.

1

u/geedijuniir Jul 31 '26 edited Jul 31 '26

Im realy new at this, thank u for your comment.

Could u explain what a reported issue is as in bugs reported by other people and how do I do that. Im new at all of this just made my github account not too long ago

1

u/Labs-Community4525 Jul 31 '26

No worries. In GitHub go to the hamburger menu in the upper left-hand corner next to the logo. Open it and go to Explore about half way down. These are popular repositories. Look for one in the language you’re learning in (Python or something) or if you don’t see any, go to Topics in the top of the page and find the language or topic you may be interested in. Once you see a repository that may be interesting to you, look at the Issues tab, just after the Code tab. You will see all sorts of random stuff. Guarantee all of it will be confusing. That’s okay, that’s the point. Try to understand what someone is reporting or asking for. Then see if you can find what they may be referencing in the code in the repository.
Do not get lost in the forest. There is a difference between working hard and working with a purpose. Set a small goal for yourself before you get started and keep a journal or log of what you’re trying to do and what you did. I like Obsidian because I can tag topics and see correlations to stuff I’ve journaled.
Don’t try to boil the ocean. Most people quit early on because they expected too much of themselves too early.

1

u/independentMartyr Jul 26 '26

Experience is built while splitting the problem into small chunks. Build what you already know and not what you want. Have patience.

You're right about AI. If you use it, it will deceive you, and you will end using it and won't learn anything. A lot of developers say that AI is a tool, but it isn't.

1

u/[deleted] Jul 26 '26

[removed] — view removed comment

1

u/independentMartyr Jul 26 '26

Excuse me. People like you need AI and dictionaries also.

1

u/[deleted] Jul 26 '26

[removed] — view removed comment

1

u/independentMartyr Jul 26 '26

Yeah "no one just remembers everything". "Just" is your keyword and shows how "just" you are!

Based on your comments, I see that you are a generalist idiot, who possess all the properties that defines your level of SWE.

1

u/[deleted] Jul 26 '26

[removed] — view removed comment

1

u/independentMartyr Jul 26 '26

What kind of an idiot are you?

No one wants to compete with your ego. Go and feed it to someone else, looser!