1, read other people's code is necessary to read the essence of them, standing on the shoulders of giants, allow themselves to be giant.
2, do not negative to read other people's code, but with the spirit of digging to find treasure other people's code in essence part, to find out where good architecture for our use.
3, understand the intent of the code of others, and then go to modify, expand, extraction, refining the essence. This is the only way advanced.
4, to understand other people's code, the code must first be familiar with the naming conventions.
5, reading the code system aimed at understanding the whole picture rather than details.
6, heart must have a sense of architecture-level, for example, if it comes to an event-driven architecture, should not think that this system there are three important roles, event scheduling, event production, event handling. Learn from the top down, to not care about the internal details.
7, from the author's point of view to understand the code, understand architecture.