Absolutely agree. Get other people to look at what you've done, and to talk about what you've done or are going to do.
Another good resource to look at is "sourceforge." You can look at the source-code of actual projects, and
you can also get a glimpse of the process that is used to build and to maintain them. You'll see their "issue tracking" (or "tickets") system; you'll see a version-control system and its "commits." You can sometimes look at a reported issue and see the actual source-code changes that were made to fix it. You can see the tests that were written to verify that the problem exists, that it has indeed been fixed, and that it will forever stay gone.
Programming is a craft,
and when you start in a craft, you're an Apprentice. Which means that you get to empty a lot of bit-buckets of their smelly ones and zeros
and do a lot of what seems like drudge-work, yet, all the time being exposed to the code and to what's going-on around you. In time, if you persist, you become a Journeyman. Then, finally, a Hacker.
(One does not become a Master. The Machine is always the Master.)