[mgomez]

It sounds like you might be stuck in a "tutorial loop". Put them aside for now, and try building a tiny project for yourself. It could be anything that interests you; scratch whatever itch you may have right now no matter how silly/useless it seems. The goal is to start writing code for something tangible (instead of learning the basic mechanics of whatever language for the nth time as you aimlessly cycle through tutorials). Your code will be crappy and unidiomatic. That's okay because after you get that first project under your belt, you'll now have a better idea as to which resources to target next to improve.

[casablancatoast]

Thanks mgomez, I think you're onto something. My only difficulty with this would be the concept of 'you don't know what you don't know.

[kirkules]

I just want to second this suggestion.

Pick a small project that you care about.

It has to be something you care about because you will pay attention to whether the results do something meaningful, which is the key to guiding you toward actually learning what you need to learn. For me, this meant making video games. For my friend a physics educator, it might mean generating random quiz questions with meaningful or realistic numbers.

It also has to be simple. For me, I started a long time ago with a text based game where you fight a sequence of monsters by basically rolling dice with tweaks and theme that mattered to me. For my friend, it might be literally randomly generating 3 random numbers and putting them into a pre-written physics problem.

There is always a way to add on to a project you care about, so start super simple and make it work really well (just meaning, to your satisfaction). Then add on another thing and try to integrate it, and so on.

My CS students when I was TAing always learned the most from long term projects that had enough freedom for them to make it fun for themselves. This is in contrast to curated sequences of academic exercises and expository text.

[casablancatoast]

So for example, creating something in pygame could be useful if you enjoy making games but don't necessarily want to be a game developer, just for the education you will receive via the enjoyment you are having making it?

[bityard]

The beauty of starting any arbitrary project. It will SHOW you what you don't know.

Some people love this phase of learning the best because it can be the most exciting part ("I hadn't even heard of topic X this morning but now I know enough to be dangerous"), and some just accept this as the slog that's required to get you up to speed enough to build useful things which is the part they enjoy the most. (I'm the latter.) But either way, that's how all of us start.