Direct impact
The code changes are directly affecting me, I will scan carefully.
Current job
Since it's a huge enterprise code base, we have multiple teams working in the enterprise code base. I often merge the development branch into my branch and 90% ignore the merged code. Now, if there is a merge conflict, then I take a look enough to fix the merge conflict.
Curiosity
If I am curious about a feature or a piece of functionality another team implemented, I take my time looking at the code and learn from it.
Every situation and context is different.
Here is mine:
Direct impact
The code changes are directly affecting me, I will scan carefully.
Current job
Since it's a huge enterprise code base, we have multiple teams working in the enterprise code base. I often merge the
developmentbranch into my branch and 90% ignore the merged code. Now, if there is a merge conflict, then I take a look enough to fix the merge conflict.Curiosity
If I am curious about a feature or a piece of functionality another team implemented, I take my time looking at the code and learn from it.
Good points. I imagine it would extremely hard to keep up with every bit of code that gets merged if you're on a large enterprise code base.
Haha it is hard to keep up. When you first start a job, you've the urge.
That goes away when you are too busy trying to get your work done. :)