Studying someone else's code. How?



  • Big project for 2,000+ files. I was trying to figure out a chain of relationships in VS2013, but something doesn't build it because of mistakes. Please indicate what tools and tools can be used to understand the structure of the project.



  • We just need to have a common understanding of what the project does and what its main constituent parts do. I mean, there's a need for understanding at the top level of the abstraction of this project, what it does, and how it works.

    It is natural that a description and documentation be provided.

    As for the study of the code, the code makes sense only to examine the one you're dealing with. I mean, for example, if you need to change a module, you're studying those module functions that are potentially related to changes. It would be desirable to have a connection with the programmer who had previously written the module or at least introduced into the module the logic that you have to change, or with a programmer who has a better understanding of the structure of the project and its functionality.

    When you change the module, you'll be a specialist in this module and its functionality. :

    For such large projects, each programmer is a specialized specialist, with the exception of those programmers who are project architects. And in principle, there's no need to know what the whole project is doing. It's enough to know the narrow range of special tasks you're dealing with in the part of the project that you've been targeted.

    Imagine, there's a Windows project. As a programmer, you really need to know just that Windows is an operating system. And you'll be responsible, for example, for the development of the conductor, and in the guide yourself for his graphic interface.


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2