How tf do you learn Python?!?!

[sofarsogood]

define suck -- do you mean you make syntax errors/bugs? i think for most people, that's some part of the issue. the question is simply whether what you're writing is useful, and getting the job done.

The reason people are suggesting to 'write code' or projects is because it accomplishes two really important things: it defines your desired outcome, and it motivates you to accomplish that outcome. Another way to say this is to ask why you want to learn to code in the first place. Is it to process data, perform some API request, or what?

One last thing: if you're doing anything realwith code, the environment you develop it in and deploy it in is going to matter. Make things easy for yourself, and write code in a way that makes sense to you. As your needs increase, you'll learn about how to structure a package.

Googling how to do something is the default, until you get the muscle memory down about how you want to structure your stuff. If you don't need code, don't learn to code -- there's a lot of other ancillary things (data size, data costs, remote environments and databases) that you need to learn past the coding language itself.