Preface
I went to an interview the other day. Most of the interview questions were very basic. There was a question about burying points. The interviewer asked me how to reduce the intrusion of burying points into business code if I did not use third-party SDKs for burying points.
At that time, I didn't think too much, so I said to create a BaseView class, carry out the operation of burying points in this class, and then make the View that needs the operation of burying points inherit this Base class. Later, I think about it, this solution actually has many problems, because each View that needs to be buried in inherits the BaseView class, indicating that the View needs to be customized, which will consume a lot of time and effort. For the buried points of the built-in Button and other controls, This method cannot be achieved. So, in fact, on this question, I didn't answer very well, but maybe the previous questions were answered well, and the interviewer didn't say anything, just said yes, and then continue to ask the following questions.
Regarding the problem of burying points and reducing business code intrusion, I came back and thought about it. Perhaps it would be a good choice to use the proxy mode to implement it.
Why systemize?
The so-called systemization is actually to sort out one's own knowledge. Only in this way can I know what abilities I have and what abilities I lack. And can quickly reuse knowledge points, saving the development time of repeated functions.
Some people will say that sorting out common knowledge systems only stays at the level of use and cannot achieve advanced effects. Yes, this common knowledge system can help us quickly reuse functions, save time, and at the same time deepen our surface understanding of functions, so the time saved and the surface understanding of functions are our advanced principles of function realization basis. From the outside to the inside is also a method.
We must not only broaden the latitude of knowledge, but also deepen the longitude of knowledge. So reading the source code and understanding the principles are our goals.
How to build the system?
sort out! First sort out the detailed function points, and finally show them in the form of mind maps.
If you feel that others have organized it well, you can link directly to other people's blog addresses without having to repeat yourself.
Android common knowledge system mind map (example)
summary
With so many excellent development tools, you can make higher-quality Android applications.
Of course, "I need to be hard on my own. " If you want to write excellent code, the most important thing is your own technical level. Otherwise, even the best tools will not be able to use its full strength.
Here I also share an Android learning PDF+architecture video+interview document+source notes collected by the boss himself , as well as advanced architecture technology advanced brain map, Android development interview special materials, advanced advanced architecture materials, these are all mine In my spare time, I will read the fine materials repeatedly. In the mind map, each knowledge point topic is equipped with a corresponding actual combat project, which can effectively help everyone master the knowledge point.
In short, it is here to help everyone learn to improve their advanced level, and save everyone's time to search for information on the Internet to learn. You can also share with friends around you to learn together
Advanced, it also saves everyone's time to search for information on the Internet to learn, and you can also share with friends around you to learn together
If you need it, you can click here to get it