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.