This is what I did when I started this gig that I am currently in.
I usually not try to understand everything, each component, because it makes me anxious. What I usually do is to ask for an small task (I.e. resolving a bug or changing a small part of UI, if you are doing front end or mobile) and I try to use that as a guide to star learning the code. Then, I ask for a different issue, that maybe solves something in another part of the code base.
I use notion to make some notes about what I am learning and try to compare and contrast with my previous projects, because that makes me think about why some things are different. “My previous project used MVP as a design pattern, the new one uses coordinators. Why?”. I write that down and start to research about the motives. At some point, I can ask somebody to resolve some doubts.
This is what I did when I started this gig that I am currently in.
I usually not try to understand everything, each component, because it makes me anxious. What I usually do is to ask for an small task (I.e. resolving a bug or changing a small part of UI, if you are doing front end or mobile) and I try to use that as a guide to star learning the code. Then, I ask for a different issue, that maybe solves something in another part of the code base.
I use notion to make some notes about what I am learning and try to compare and contrast with my previous projects, because that makes me think about why some things are different. “My previous project used MVP as a design pattern, the new one uses coordinators. Why?”. I write that down and start to research about the motives. At some point, I can ask somebody to resolve some doubts.
I like that part about writing down what you’ve learned/currently doing. I don’t do that enough that would definitely be helpful. Thanks!