Knowledge System

It's been fourteen years of work. I have done three years of networking and eleven years of development and management. Usually, I rarely have the time and emotions to sort out the knowledge system for so many years. Half of it is because of my own knowledge, realm, and experience. I think that writing is actually a very sacred thing. Without accumulation, it is difficult to grasp the whole picture. Personal character, with a life attitude of only asking about hard work, not about harvesting. Today I am interested in sorting out my knowledge structure.
1. Basic knowledge
2. JVM
3. Design patterns and principles
4. Application framework SSH
5. SOA
6. Storage (sql, nosql)
7. Search
8. Big data, cloud computing
9. Mobile terminal development
10. Software engineering methods
10 1. System Architecture
12. Performance
When human beings think, God laughs. Everyone has their own three views. My own development philosophy or architectural view is basically as follows: focus on the foundation, think about the structure, and save the application.
Re-basing refers to mastering the characteristics, advantages and disadvantages, operating mechanism, and best practices of the development language.
Thinking architecture refers to macroscopically guiding, designing, deconstructing business, technology, and stakeholders in the organization, and making them work organically.
Storage applications are specific solutions for specific business types. Technology is not good or bad, only suitable and inappropriate.

Maybe there is an inaccurate vocabulary expression, maybe the depth of thinking is not enough, and remember it.