Architect's learning experience summary

The 3-month architecture study is over soon. Looking back on the past courses and assignments, I have the following experience.

The curriculum is designed in multiple areas, even if due to time constraints the curriculumEach area has not been explored in depth.But knowing these areas has been helpful.My personal experience is that when developing a system, the difficulty is not in solving the problem, but in finding the problem.When thinking lacks enough breadth, design has blind spots.As an architect, obvious blind spots should be avoided.A systematic understanding of the common areas that need to be evaluated to develop a system can go a long way in eliminating blind spots.

Architecture learning is not so difficult, if the relevant knowledge can be reasonableClassification can be integrated.For example, redis and memcached are also caches. By understanding the usage of Redis, you can roughly deduce the usage and characteristics of memcached.We only need to compare the differences in performance, functions and features between the two.

Systematic learning is of great significance, and learning in the past is very importantIt is easy to focus too much on a certain technical detail, while ignoring the significance of the technology to the overall architecture design.If someone can systematically generalize the meaning and role of various technologies on the overall architecture, this generalization will be very helpful.

Finally, even after the course is over, we still have to continue to learn various technical details. After all, the devil is in the details, and the more we grasp the details, the more reasonable and easy the architecture design will be.But the learning at this time will be systematic, targeted, and efficient.