maybe we could do it this way or that way

This is where a team coding standard, naming standard, and formatting standard really helps.

You're always going to receive feedback on your code. Part of what makes coding fun is that there are a million different ways to make something that works and most people are going to think their way works best. More experienced engineers most likely do know a better way to do it, so take their suggestions, figure out why it's better, and apply those principles to all of your code. But sometimes junior level people come up with great ideas. It's important that you know why you made certain decisions, and to be able to defend those decisions. After considering recommendations, consider if they are actually better, and if you think they aren't, then have a conversation about that.

If you don't have experience working with dynamic data then it's normal that you just forgot that you needed props instead of text (or whatever your situation was). Now that you made that mistake, you'll probably never make it again.

Don't be too hard on yourself. There is too much for any single person to remember. I've been doing this for 20 years and I still have my head in the docs several times a day. On that note, make frequent and liberal use of the documentation. It's okay to forget stuff you haven't done in awhile. Yesterday I forgot what the freaking span element was called and I've made spans a hundred million times before. It just poofed out of my memory. What's not okay is not knowing how to find the information you have forgotten. Again, learn the docs and use them religiously.

Always remember that there are two states to every programmer. That link is a funny but accurate reminder of something we all experience..

Good luck. We're all counting on you.