I’m also self taught and two things that helped me are, ok well 3 1. Read clean code 2. Read clean architecture Or at least find someone summary of the books.

I’m also self taught and two things that helped me are, ok well 3 1. Read clean code 2. Read clean architecture Or at least find someone summary of the books. They helped me feel more confident in the code I wrote, the way I wrote it, and helped me justify why I wanted to write it the way I did 3. Look up DDD - domain driven design. I think that starting to learn about different architectural methodologies will help to understand bigger projects better. It’ll also help you to see where the projects went wrong, and sometimes that’s reassuring too because it shows even senior and principal devs don’t always really know exactly what they’re doing This is a good GitHub repo for DDD. Definitely look into others as well, not saying DDD is the answer to all problems or the best for any, but I just like it lol :shrug: https://github.com/heynickc/awesome-ddd https://github.com/heynickc/awesome-ddd