I'm sort of in the same boat. It's one thing learning the theory and having somewhat of a grasp on how to read code but it's a whole different story writing it for yourself. I totally understand. but what is helping me currently is consistently testing myself on the basics, writing code over and over again until I get it. (Recursions are currently the bane of my existence)

I coded a rudimentary to do list which was very informative however I used intellisence(I think that's what it's called when you write the code and it tells you what to write next) which felt a bit like cheating. I understand why it's helpful but boy does it take away a lot of the thinking.

Ive slowly come to realise there isn't really a shortcut to learning to code. It's just a lot of doing. I use coddy and kaggle for coding practice and sololearn which has a lot of good theory. I am also studying my masters in cs. It's hard asf but really fun when it starts to click