When developing on a large project, how do you find out of the scope of your part, and how do you generally explore the project beyond the task?

Question

Career in IT

Periodically, such tasks arise when, while making changes to your part, you also need to make them to the part on which you did not have to work. And sometimes you need to study that part first. Well, or not even to study and not to contribute, but to make sure that the appropriate person is in the know and will contribute them there.
What happens if this is not taken into account?
At best, your mistake will be pointed out to you. And it would be better if you do it yourself...
In the worst case, no one may notice the problem in time, because the main specialist in that part does not review your code, and those who review, even if it is the team leader of the whole team, may not know such details.
And okay, if the modules are connected directly. There, nothing prevents you from understanding that you need to get to the bottom of all the modules created by your team - and look at all these modules. And, perhaps, to understand that the emphasis should not be on your module at all, but on the deepest one.
But if "that" module is stuck somewhere on the side, then even knowing about its existence and principles of operation, you can simply forget that the next task is connected with it.
The first question is how to deal with it?
It is stupid to ask yourself a clear question on each task, "What is behind this?"
Or is it better to study someone else's part even earlier, and remember under what tasks to ask such a question regarding this part?
And then the second question - what is the best way to study someone else's part?
It’s even easier for the team leader, because he and all the merging code can follow if he wants (and often he should), and at the same time he discusses the architecture with the participants verbally.
And how can a simple jun do it? Nothing but the embedded code is inaccessible to his eyes? Or are there also juniors who are also available for verbal discussions? Or is no one present at all studying someone else's code of their team?

Answer 1

this is the wrong approach. if everyone saws only their own piece, then you will never get such a task. otherwise, there are no "foreign" pieces, but only "so far unfamiliar" ones. I don’t know what can be studied there in advance, I have never done this. I just threw small tasks from different parts to each newcomer on the test, so that the project could be stared at as much as possible.
if necessary, the lead was told that the execution time would increase, because you have never climbed here and you need to figure it out, read the code, looked at the repository logs, what has changed recently and for what tasks, maybe debug those pieces where it is not obvious. made a task, asked the lead to review it himself or delegate it to someone responsible.

Answer 2

If there is a team leader, then you definitely need to contact him. Because June can be sure that for the sake of his edits, you need to redo half of the finished code and earn candelabra from those who debugged it. And the team leader will poke him with his nose in a simple and natural way not to break anything superfluous. Even if it takes ten times the time of that green june.

Answer 3

1) You take the task into development
2) You study the code
3) You tell the manager (tech lead) that you don’t understand anything here => it will take more time than usual
4) You tell the testing department that you don’t understand what you did at all - let them test your edits more thoroughly.
Something like this =)