Recently, a lot of people privately asked me how to become an architect, and one was confused about the current state. I will make a simple explanation here, or it may be a little help for you who are confused.
Are you currently feeling lost?
There are many people who feel very bored with their current work, because the current work is all about realizing business, and there is no improvement in technology. In this state, you will feel confused, especially when you think of the future, this feeling of confusion will be even stronger.
Rather than being confused, it is more worrying. As time goes by, my technology has not improved, so I feel worried.
There are two types of people here:
-
mess around, one day counts as one day
I won't discuss it too much, it's pointless. I have also met many colleagues like this, and such programmers are already useless.
-
If you want to improve your technology, work hard in the direction of the architect.
Most of the people who send me private messages are this one. First of all, it can be seen that these people have their own ideals, and they will also put them into practice. I want to go in the direction of architects, but I suffer from no one, and I don't know how to become a framer. If it doesn't change, such programmers may also be obsolete.
I want to use this article to talk to you about the topic of architects. It is purely personal understanding, and there is no need to worry about right or wrong.
The definition of architect?
Personally, I think architects need to have the following characteristics:
-
Breadth of knowledge: Need to know why mainstream technologies were born and what problems can they solve? If the same business is implemented with different technologies, what are the advantages and disadvantages? For example: the popular ORM framework Mybatis and hibernate, what are the advantages and disadvantages between them? Having a clear understanding will allow you to make the right decisions when it comes to technical styling.
-
Abstraction capability: abstract business and technology. Business abstraction is to establish the perfect entity class and the connection between them after analyzing the requirements. Technical abstraction is a layering of the overall architecture and the interaction between layers. This is crucial, if the technical abstraction capability is insufficient, it will lead to an inflexible architecture of the entire system, which is difficult to maintain and expand.
-
Depth of knowledge: At least an expert in a certain field, such as a message queue, activeMQ is familiar with its source code and knows its implementation.
-
Excellent learning ability: learn new technologies and cutting-edge technologies and use them to solve business problems at work.
So how do you go about it? I think you can start with the following steps:
1: A solid JAVA foundation, the content introduced on Think in java can be understood, and congratulations on becoming a programmer for this step.
2: Proficient in using mainstream frameworks, such as: mybatis, spring, etc.
3: I have studied at least one source of web framework, such as spring mvc, struts, etc.
4: Have architected or participated in the design of excessively concurrent systems, and know how to deal with emergencies.
5: For the business in which you are located, you can put forward optimization suggestions or predict its risk points according to your own knowledge dimension.
In fact, whether or not he can become an architect has a lot to do with opportunities. For example, a programmer has done all the above, but the company has not given him the opportunity to do it, a real opportunity for architecture. Because the previous architect didn't have a chance if he didn't leave, this is the reality!
Many people do not know how to learn the knowledge required by architects, here I share with you my favorite video tutorials:
If you need to pay attention to all the video tutorials of the architect, you can get the above learning materials by sending "Architecture" in a private message.