It took me a few attempts to teach myself: 1) started drag&drop with simple logic using Delphi. It was fun but eventually ran out of ideas for problems to be s

It took me a few attempts to teach myself: 1) started drag&drop with simple logic using Delphi. It was fun but eventually ran out of ideas for problems to be solved and moved on to 3D modelling and then life happened. 2) Some years later, started watching some MIT videos where some math professor was teaching python via mathematical problems. It was awfully boring,so I stopped shortly after. 3) Got a job that eventually evolved into doing technical things. Got bored and started learning basic programming so O could solve more complex business problems. O was hooked. Automations, efficiency going up,etc. It all started from really basic database triggers and then gradually was getting more complex with integrations and etc. I've also tried many tutorials,in the same way you did. For instance, recently I've tried Erlang. The language is beautiful but got stuck for hours in like step 3 because of some odd database related issues. It took much longer than I thought it will. The same with JAVA and Maven,etc. I think getting stuck on the infrastructure as opposed on the actual programming problems is very often problem. It's super frustrating, but what it does eventually it requires you to stop and really understand what os going on with that command line, some DB connection or a particular version. It's slow, painful process. If you manage to go through it,many many things become much easier afterwards.