If you want code reviewed, contribute to existing projects.
Part of getting better is realizing the previous work needs to be rewritten. Your past self wouldn't have known that at the beginning. But you got better.
For example, I'm not new to programming, but am new to Go and have been struggling to figure out how to model messages as structs using composition rather than inheritance.
As one of, if not the most senior developer in the team that I work on, I have nobody to ask questions to, and even though the answers are out there, on the Internet, I'm still confused by them, which, IMO isn't super anomalous, but, still leaves me in a place where I'm yearning for feedback.
I found this answer on StackOverflow about Go structs for composition. It's interesting because at least there's an example of how not to do it (in Go) and a detailed answer:
https://stackoverflow.com/a/70100167
The Ben Franklin approach: "I've seen one more way not to write it."
Hope you find or figure what you're looking for.