"how can an inexperienced junior programmer with poor skills read the project source code?"
"has anyone read the source code of mybatis? just look at the initialization process and get dizzy. Friends, give me some advice!"
"how to read the source code? I have tried to read some source code, such as the sqlparser part of the druid of alibaba, but spring-mvc, found it very difficult. They all say that debug is the best way to read. I often lose track of it when I am in debug. It is just that walking feels like I have entered some details that I don"t pay much attention to at present."
.
it is estimated that many people have such doubts.
I can understand the pain of my friends very much, because I have come here in the same pain.
the benefits of reading excellent source code must be known to all, learning other people"s excellent design, reasonable abstraction, concise code. In short, there are a lot of benefits.
but really put a huge code in front of you, just like a huge maze, it is really not easy to find a way to turn west in the Middle East to figure out the whole structure of the maze and understand the core ideas.
when reading code written by object-oriented languages such as Java, you will find that interfaces often do not correspond to specific implementations, and it is not clear exactly how a function can be found in which implementation class. Unlike the C language, it is a function to call a function, which is relatively good.
if it is a dynamic language such as Ruby,Python, the type of a variable is not even easy to know, which makes it much more difficult to read.
there is another important reason. Now the source code we see is basically developed for several years and constantly improved by many people. There are so many branches and vines that the devil is in the details. When reading, it is easy to fall into it. After watching dozens of layers of function calls, I am completely confused and give up: no matter you blow up the source code, I will never look at it again.