Background:
Today received a buddy’s phone, said, very depressed, and I want to chat.
I asked, what’s depressing? Tell me.
I was planning to become an architect this year, but no matter how hard I try, I don’t know why, I feel hopeless…
This guy is actually a very hard working guy. He used to be the best technical programmer in my Team. He would not give up until he understood the technology.
I called him and said something I had always wanted to say, but never had time to say, which was: Why don’t you ever become an architect?
What is an architect?
In fact, the concept of Architect does not exist from the birth of the program development profession. Software Architect is a position that has been proposed in recent years. It seems that the concept of Software Architect was invented by IBM. However, what architecture is like for a position, just like cloud computing, looks beautiful, however, everyone has their own understanding.
Many people think that an architect is a system analyst, someone who gets to analyze system requirements. Wrong! If systems are just systems analysis, who’s going to do architectural design?
Some people think that an architect is someone who designs architecture, draws UML, writes documentation, etc. Wrong! Is drawing UML design? Who drew it? Who designed it?
Some people think that the architect is subordinate to the project manager and has no authority over the design. Wrong! Does a design have weight if the decision is left to the project manager?
What is an architect?
Without answering, let’s take a look at some of the job descriptions that predate the concept of architect.
Before the concept of architect came into being, Microsoft was the model for the R&D organizations of most of our software companies. At that time, the popular combination of positions was — technical manager + Project manager.
Ok, of course there are many companies where the technical manager and the project manager are actually the same person.
That is, most enterprises adopted the development director responsibility system, that is, the person in charge of technology + team + project.
When we take the “project manager” out of development and only manage the progress of the project and remove external obstacles to progress, the person in charge of developing the technology and the development team is the “technology manager”.
It would be easier for all of us to understand if I told you that the former technical manager is now the architect.
Yes, it is, if the “architect” design loses the “voice”, “technical direction decision-making power”, “team members development resources allocation power”, then we can imagine how weak the design!!
So what is an architect?
The architect is a team of TeamLear who has the right of technical voice, direction decision, and resource allocation of team members. He is also the designer of this program. Of course, he is the soul of this program team!
Therefore, if you don’t want to be a programmer at Teamleader, you can’t be an architect in the real sense!
At the same time, the architect who is not the Teamleader is also the architect who is on the shelf and weak!
How can I think like an architect?
An architect, who simply turns requirements into programs, is not an architect. It is called “copying the gourd.”
An architect who is only proficient in various frameworks, such as S\S\H technologies, and uses S\S\H technologies to describe user requirements is called “applying S\S\H to the schema”.
Ok, no pun intended, so how to think is the way architects should think?
First of all, is architecting without design an architect?
This is all too common in the software industry!!
Why is there no design?
Because, many people do not understand what is called design!!
Just to give you an idea, what is design? –
Design exists for the future!
— Bells, June 2010
Nothing for the future, only for the past, that is absolutely not design, that is absolutely just imitation!!
Design exists for the future!!
That is, no innovation, no design!
That is, no change, no design!
Think about your design in terms of evolution!
Let your design transcend all theory!!
Design is only the carrier of memory but not the whole memory!!
Programmers are artists, not builders!!
So why can’t you ever be an architect?
Do not only from the point of view of technology blindly in accordance with their own natural direction to work hard, to learn to use the thought of design, and strive to make yourself a significant person!
1. Those with 1-8 working experience do not know where to start in the face of current popular technology.
Need to break through the technical bottleneck can be added.
2, stay in the company for a long time, lead a comfortable life,
But I hit a brick wall in my job interview.
Need to study in a short period of time, job-hopping can be added.
3. If you have no working experience, but have a solid foundation, you are familiar with Java working mechanism.
Common design ideas, common Java development framework master skilled, can add.
4, feel very good B, general needs can be done.
But the knowledge points learned are not systematic, it is difficult to continue to break through in the field of technology can be added.
- Group number: Advanced Architecture Group Java Advanced Group: 180705916. Note good information! Send architecture video.
6. Ali Java Advanced Cattle live explain knowledge points, share knowledge,
Years of work experience sorting and summarizing, with a comprehensive,
Establish own technology system and technology cognition scientifically!