How to read the source code of other android projects?
I joined a company through an interview some time ago and began to read the source code of the project they had worked on. So I have some feelings. I would like to share with you here. It may be difficult for most people to read the project source code. First, the first obstacle: give up when you see the project! If there are 10 or more people, this may be the case above. Analyze the idea: How can I read so many codes! I want to read it for a long time! Forget it. Let's take a look at the demo. In this way, they just import the project to eclipse, click a few mouse clicks, and then there will be no more details.
Solution: in fact, the reason for their termination is very simple, that is, it is too troublesome. Well, tell you that this problem can affect you. In fact, your development path can also be terminated. To learn anything, you must spend time, energy, and preparation for difficulties. If you want to enter the sky in one step, it is possible that, unless you are a genius, but after all, there are too few geniuses! For development, I don't want to learn 1 + 1. So, Let's adjust your mind first. What kind of mentality should you have? That is: Prepare for difficulties and have the confidence to solve their sufferings. The mentality problem has been solved, that is, the code reading technique. Many people don't know how to get started with a project, so they just read it in a random manner. When they see it, they find that they cannot proceed, and began to reorganize their own ideas. This is a waste of time. In fact, it is best to take the following steps for reading a project (personal opinion, for your reference only ):
1. Use this application or game until you are familiar with its use process and functions. 2. Analyze the code implementation based on your own experience (overall) 3. If there are conditions and the original author asks the project idea 4. Starting from the first activity to start, he can understand how each activity function is implemented and how it is laid out. 5. He may encounter unintelligible code, search engines (generally ). If not, you can ask others. 6. Summarize the new knowledge points and review them on a regular basis. 7. The most important thing is: I think you need to write it by yourself, you may need to re-write the project, or design a similar project, or write only a part of the project.
Why do you need to do it yourself? Everyone knows about coder. It makes no sense if you learn the best theory and don't do it! Therefore, you can solve the problem and learn more. This is experience. to succeed, you must first trust yourself and win the trust of your friends!
