No. My post on this is extremely opinionated. But in my experience, hobbyists learn nothing from university and those who do learn from university write terrible, scrawl-like code until they gain real experience. You can skip this by going straight into real experience. Your own code always teaches you more than whatever a university tutor can, as they try to cater for everyone and teach principles from a diagrammatic point of view. If you code yourself, you will instead learn from an entirely pragmatic, usable point of view.

The important thing is going about self teaching the right way, from a variety of good sources. I personally started with video courses and online courses, then went into official documentation and then went into books. I also found myself a couple of very experienced mentors, who were also self-taught and earning big money. They had experience in a different language, so they helped me only at the very start, to teach me fundamental concepts hands-on, and to critique my code piecemeal, so that I wouldn't get overwhelmed with feedback.

Start with decent beginner courses like Pluralsight and focus on clean code, following good principles as you learn them and keep the search for decent architecture in the back of your mind. Do these things always.

After a few weeks of basics, create a "very simple" console project on something that you want to build, and iterate on it until it becomes massive. It'll break and become unwieldy, which is fine. Refactor it, prototype replacement components, build frameworks to support it, and stick with it. 

You'll learn a rediculous amount. After your outgrow video courses, read documentation documentation primarily. After you exhaust most of that, begin reading books to fill in the gaps and push for advanced concepts, things that push you to do better, instead of regurgitating what you already will have learned - books like 'Framework Design Guidelines' are good. 

As you start to accumulate a couple of books worth of knowledge, can power your way through ideas that you have, and have consumed a large amount of documentation and can see the pros and cons of your language more than clearly, then now might be a good time to expand into other languages if you do choose. But don't mix languages until you know one inside out, the pros and cons for every line you write, how everything works under the hood (up until the point that it doesn't help you write better code). 

Note on video courses: Some people like YouTube tutorials but I'd avoid them as they're slow, low quality and make it too easy to avoid critical thinking. Video courses are a good way to start just the first few lines and start thinking in code. Trying to learn without someone speaking, right off the bat, in my experience becomes too difficult and dry until you've established a bare bones foundation to build from. At that point, for me, learning from documentation became easy, and interesting, as I was striving to fill gaps.

For the language, start with something simple but well documented like C#, Python. C# is statically typed which is a bonus. Use typescript instead of JavaScript, for example. Languages which are easy to learn and well documented are great, these two examples are also versatile.

Note on AI: don't use it to write code, but it's fine to spitball ideas, critique what you've written, and learn more concepts. Don't trust it, always verify with external sources.

Stick with one main project and a series of mini prototypes and test sandboxes in order to learn fastest, in my opinion, as it gives you experience refactoring bad, unwieldy code, and prevents you from hitting a wall and abandoning to do something else. 

To find a mentor, or ask for advice, such as code reviews, there are a lot of communities for example discord. You can search for servers, ask people you know. If you play games, just check your friends list for anyone that plays factorio.

Good luck, don't let university waste your time.