Curiosity is fine, but don't let your curiosity become a distraction strategy for avoiding the real work and your eventual mastery of at least one programming language.
You will at least need one programming language to get yourself started, this will become the firm ground you need to stand on to do actual work and to propel yourself to learn the other fundamentals of programming like data structures, algorithms, etc.
And after mastering that initial programming language, your speed working on projects will increase dramatically, since you won't have to stop yourself and google for a solution every time you run into a little bit of a syntax problem. Now don't get me wrong, you will still need to google for stuff from time to time. It's just that you will stop wasting time on googling for the same information over and over again. And if you do enough exercises, you'll find that some core syntax at least becomes an integral part of your fingers muscle memory.
That being said to get yourself started, you should measure yourself against other developers (which can be a very sobering and a very humbling experience).
Use the following:
http://codewars.com (easy, I like it because it's crowdsourced, its hides spoilers from the comment section of each problem, and it shows you the many different working solutions of others, after you've successfully completed a particular problem. This site will only allow you to register and look around once you've completed two or three super easy problems)
https://leetcode.com/ (harder, use the free parts)
https://pramp.com/ (much harder, as this site makes you pair up with other job hunters to practice technical coding interviews with a shared code editor and over video conference. This is the closest thing you'll have to a real technical interview. And this lets you experience technical interviews from both the perspective of the interviewer and the interviewee, as you both take turns switching roles and the website supplies each of you with a technical problem and the solution).
Just don't let yourself get discouraged. You can become a productive developer, even before reaching the stage of the Pramp website. It's just that you need to learn honestly how wide of a gap there is between yourself and the developers who work for top tech companies.
Use spaced repetition to master the syntax of that initial programming language. Take a formal course if you can. If you can't, there are free online courses online. That kind of structure helps. Work on your own personal projects. It's easier to learn when you're trying to solve an actual real life problem. Pair up with others to form a study group. Teach others how to program in real life, or through a blog. Get a job using the programming language you've learned. And don't stop practicing. It's very easy to slide back if you don't actively maintain your gains.
After which, feel free to explore any other technology or tools you want. In fact, it is important that you keep up with the latest best practices and other tools of your profession, and adapt your skills to the ever changing market conditions.
Of course, our profession is full of people evangelizing easier paths, magic pills, and the latest hyped technology. And you'll reach many dead ends following all those leads, but it is still important that you take some time to investigate what's out there. Over time, your BS detector will become better. And over time, you'll find some tools/technology/practices that may indeed be worth switching to or adding to your toolbox. But again I must caution you, all of that will be wasted time if you don't master the core syntax of at least one programming language initially.