What are some goals a Beginner Self-Taught Developer should have?

Lead Developer here, completely self-taught. No degree, no formal education in CS. In my opinion..

• It's more about thinking than it is about slinging code.
• It's 10 x more about learning and research than it is about syntax/frameworks. - if you do Coursera's Learning How To Learn you'll save yourself years.
• Little and often is more effective than single big sessions.
• Persistence > Knowledge.
• Understand how your subconscious mind works and how you can lean on it to solve problems.
• Get plenty of sleep.

Learning syntax is the first step, but it is incredibly important to learn to create readable code. Writing code is like writing a paper. Getting the code down and the logic correct is your first draft, but what makes good code stand out from bad code is the extra effort put in to revise and refactor it into something that is robust, readable, and reusable.

Patience. You cannot learn everything in a day. Take your time, now is probably the best time in the history of computing to learn... You have more resources to learn (information freely shared, computing resources, etc...) than ever.

Learn to estimate your work.
The transition from "let's try something fun until I'm tired" to "How long would your suggestion take?" is hard, especially for self-taught devs.

Set yourself "observable milestones" such as "Print button actually prints something nice", give it an estimate, write that down, and track your time. Compare.

Be honest with yourself. Did you really complete the milestone, or does the "print" button print something plausible, but not actually what you need?

This requires the almost mechanical skill to track your time spent, the mental focus to stay on topic (instead of fixing whatever crosses your path), and the most artistic skill of coming up with a useful estimate.

(Estimation can be a black art, don't want to go too deep here. But even with the first two you are already ahead.)

Include all artifacts
It's the most common mistake in estimation, and the one that devs can still get wrong after years: Print does print, but the manual isn't updated, some more tests should be written, the keyboard shortcut still needs to be wired up and setup needs to include the Printer Abstraction Adapter Runtime.

The feature is not done until it can be published.

Publish
Have someone use your software. Ideally, watch them using it. Find some sympathetic victim, offer some prize money, whatever. This is the best answer to "Am I finished?" you'll ever get - and self-taught devs tend to lack that experience.

Go back
Come back to your code base after half a year or more of inactivity. Fix a bug and add a feature.

Teaches you humility and maintenance, which is roughly 40%...80% of development work.

I'd develop a really well-made portfolio of various projects so people can immediately understand what you're capable of.

Being able to make 'things'. It doesn't matter if they are super technical or anything just being able to apply the theory or stuff you've read will cement it in your head and you will find that your problems are no longer in writing the actual code but to visualize the systems you create and bringing them into being. As a CS uni student, the thing I see most often are students who study programming theory a lot but can't contribute much in actual projects or what not. Also, it's nice to look back on the projects that boggled your mind a year ago and to have a nice laugh at your former self

I think that understanding set logic and boolean logic will go a long way towards helping you understand some of the higher order stuff people are doing, but you don't have to understand that on day one.

Just because there's a pattern to the code, doesn't mean you need to memorize the pattern. You should learn the reason for the pattern. That's how you become a better developer, knowing why the pattern, so the pattern becomes second nature.

Learn Git. Make a GitHub account.

Start projects and more importantly, finish them. (and put them up there, of course)

Connect with other developers, there are plenty of Slack/Discord/Gitter servers. (I can invite you to our own Discord server) It's fun interacting with other devs and you learn a lot from it.

If you want to work in this field: Understand the business value you cant always write the fanciest code just because you want to. Often it has to be practical: cheap, short timeframe and maintainable for many years to come by someone other than you