It's good to try different things out to see what you'll end up liking. Doing a short course or a short college degree on anything will give you enough of an idea about the field for you to know if it's something you'll want to pursue or not, and paid internships could give you some insight as to how work will be in that line of business (or not sometimes).
The problem comes with the fact that, nobody has infinite time to figure out the best career for them. Expenses come fast and these decisions take much longer than a single month to make, so you'd need a fallback plan. Preferably, you'd want your fallback plan to be something that's always in need and that won't absolutely drain your energy every week and will leave you with enough free time to focus on learning whatever else you want to pursue. That's more or less what I did with accounting during high school. I do well enough with accounting and the numbers and the spreadsheets and stuff, but taxes and the legalese stuff absolutely drain me.
After the fallback plan, well, it's back to experimenting and trying things out. Things worked well for me because multiple people were recommending I go to college to become a programmer, and then a year passed since I started college and now I'm a web developer I guess. But in my case, my interests aligned with a field that's very much in need. IT in general is just a very broad field with many career paths.
Do I like what I do? Yeah, actually. Although I usually go against contributing to the bloat of web libraries, my work deals with making SAP solutions, basically ERP-like applications with a database, back-end code and front-end code for organizing internal processes and stuff. Because these solutions need to be contained within the 'SAP ecosystem' (which is basically what I call the array of different services they provide), and since I make front-end code, I absolutely must use the absolute unit of a bloat library that is SAPUI5. How bad is it?
20.8MB (1.34.7 runtime, minified, zipped)
6.8MB (1.34.7 runtime mobile, minified, zipped)
52.1MB (1.34.7 SDK, zipped)
Yikes. SAP is kinda like Apple in a way, but for corporations instead of consumers. The only reason business use their services is because it's SAP, and if you have a bit of your system running on an SAP solution, then it just makes sense to convert everything to SAP to prevent integration issues. But like I said, these are internal solutions, so the people using these programs will be using the intranet rather than the internet (for the most part). Anyway, this is just my experience so far with careers and stuff. I'll probably be seeking to learn more about web-related things, both SAP (for work) and non-SAP (for academic purposes, hobbies, projects and etc.) as well.
There's no real formula for finding the right career. You can either jump in to fields that are in need, or try for a field that's less in need but that you're more confident you're gonna like it.
There is a japanese concept of 'Ikigai' but really that just helps you categorize your potential career paths between 'what I'm good at', 'what I can be paid for', 'what the world needs / what's in demand' and 'what I like doing / what isn't going to emotionally drain me'. If you're confronted with too many options, Ikigai can be a nice way of organizing them. But if your problem is a lack of options, then it sorta falls flat until if you find more opportunities. All and all, it's just complicated.
____________________
"The quieter you become, the more you are able to hear." --Ram Dass
