Architecture is a good step to understand the whole software. I would add, outside of looking at the code to understand what happens, ask question, i believe there is no wrong question(although not all team/manager agree on that) but by asking those question early on you gain knowledge way faster.
The other important part is to not hesitate to know the things that are outside of you job description. I once was working on a very large organization (as a low rank developer) and because i was chatting with people from other team asking questions to our DevOps about how our software was deployed, asking our incident manager what where the process in case of major crash, asking them the why and how of any desktop settings or constraint you do become the go-to persons from your team(and sometime from sibling teams) but you are also in a position to unblock administrative issue and lead your team to become a performant team in a context that usually prevent it. Even if in a smaller more flexible organization it let you solve situation without load of meeting and getting many people to understand a situation to find a solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Architecture is a good step to understand the whole software. I would add, outside of looking at the code to understand what happens, ask question, i believe there is no wrong question(although not all team/manager agree on that) but by asking those question early on you gain knowledge way faster.
The other important part is to not hesitate to know the things that are outside of you job description. I once was working on a very large organization (as a low rank developer) and because i was chatting with people from other team asking questions to our DevOps about how our software was deployed, asking our incident manager what where the process in case of major crash, asking them the why and how of any desktop settings or constraint you do become the go-to persons from your team(and sometime from sibling teams) but you are also in a position to unblock administrative issue and lead your team to become a performant team in a context that usually prevent it. Even if in a smaller more flexible organization it let you solve situation without load of meeting and getting many people to understand a situation to find a solution.