Welcome to Code Forum!

Join a community that supports you and your coding journey from day one. We strive to be a friendly, supportive community that empowers everyone to be better developers. By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!
  • Guest, before posting your code please take these rules into consideration:
    • It is required to use our BBCode feature to display your code. While within the editor click < / > or >_ and place your code within the BB Code prompt. This helps others with finding a solution by making it easier to read and easier to copy.
    • You can also use markdown to share your code. When using markdown your code will be automatically converted to BBCode. For help with markdown check out the markdown guide.
    • Don't share a wall of code. All we want is the problem area, the code related to your issue.

    GIF shows where to locate </> in the thread and or post editor toolbar.
    To learn more about how to use our BBCode feature, review our "How to post your code into threads" here.

    Thank you, Code Forum.

Python Learning process

Greko

New Coder
Hello guys I need help with my learnin process, I am just start learning py by myself and I need to know if I need to know evereting before I can continue with the next topic ?
 
You do not need to finish one topic before touching the next. Programming is not learned in a line, because the same ideas come back in harder forms and land better the second or third time you meet them.

The practical split is between what you must understand before moving on and what you only need to have seen. Loops, variables, functions and how to read an error message belong in the first group.

Decorators, generators, threading and most of the standard library belong in the second. Meet them once, remember that the name exists, then move on.

What makes the difference is having something you are trying to build. Following a tutorial to the end teaches recognition. Typing your own small program, breaking it and fixing it teaches the thing itself. Pick something slightly beyond where you are, and let the gaps show up as concrete questions.

Keep a short note of the concepts you skipped and revisit one when a project forces you to. The order then follows your work instead of a syllabus somebody else chose.
 

Buy us a coffee!

Buy me a coffee.
Back
Top Bottom