Realistically, you should still find a project that you want to do and use that as the basis of your learning, as that will influence your language of choice,. I'd start with either python or powershell stuff to get going, as both are general purpose, multiplatform languages that can do a lot and are moderately forgiving with syntax and stuff.

Past that, find a project that interests you, break down what needs done, and learn those steps individually. It's not as cohesive as a hand holding hello world style tutorial, but I found I learned so much better if I had a need for the knowledge instead of just learning for it's own sake.

In my case, I picked powershell as I'm a windows admin. Since I'm a data hoarder as well, I chose a video conversion pipeline to convert all of my movies into a consistent file format. Part of the requirements are to find all files with an extension that isn't my standard (concepts: file listing, filtering, working with objects) and then execute an external program to convert the files (concepts: command line execution, state management, error handling, looping), validate the conversion completed successfully (concepts: reading file content, filtering/regex), moving the files to a new location or replacing the file with the new one and backing up the original (concepts: file management), and log file retention and cleanup. As I developed my script, I also began learning to properly "function-ize" my code to make things more readable/usable, and eventually started moving functions into a module to better modularize my code.

A decade later and I'm currently in the middle of a couple of projects using powershell to make and call API functions to automate business services at work.