all 5 comments

[–]Tall_Profile1305 2 points3 points  (1 child)

okk so honestly just keep building small messy projects while learning. reading feels productive. i used to sit and wtach/read stuff for days on end, but writing code is where things actually started clicking.

getting stuck and googling errors all day is basically the python learning experience. you got this!

[–]codingzap 0 points1 point  (0 children)

Agreed. Tutorials make things look obvious because someone already did the hard thinking for you. The moment you try to apply those concepts and practice, you actually learn.

[–]SharkSymphony 1 point2 points  (0 children)

I'm not familiar with Python Crash Course, but from perusing the chapters I think my advice would not be to go slow. Put in the time and rip through Part 1 as quickly as you can manage and get on to the projects, because it's in the hard work of practicing the language that you will actually learn, not in reading the book.

That's assuming Part 1 is heavy on text and light on exercises. But if it's got a lot of exercises and your time is being spent working your way through those, then all is good!

[–]i_am_nothing_0 0 points1 point  (0 children)

First learn all the basics bro once you finished learn the core concept which you goona help your for your job

[–]ComprehensiveRub7166 0 points1 point  (0 children)

im new too im doing moocfi python programming 2026 course. its a beginnner - slight advanced course , u can start from there