Why can't you become an architect?

Why can't you become an architect?

 

Background:

Today, I received a call from my buddy, saying that I am very depressed and want to talk to me. I asked, What is depressing? Let's talk about it. He said that I was very depressed recently. I planned to become an architect this year. However, no matter how hard I work, I don't know why. I feel very hopeless... This guy is actually a very hard-working guy. He used to be the best programmer in my team and never gave up on a technology. I told him over the phone that I always wanted to say something, but I never had time to say anything. That's why you can't always be an architect?

 

1. What is an architect?

In fact, the concept of architect is not the concept of a job that was born from the programming profession. The concept of architect is only a position proposed in recent years, it seems that the concept of software architect was proposed by IBM. However, what kind of role is architecture, just like cloud computing, which looks very beautiful, but everyone has their own understanding.

Many people think that the architect is a system analyst. He is the one who gets the system requirements for analysis. Wrong! If the system is just a system analysis, who will design the architecture?

Some people think that architects are architects who draw UML and write documents. Wrong! Is UML a design? Who is the person who designs the drawing?

Some people think that the architect belongs to the project manager and only manages the design. No matter what the right is, it is wrong! Assuming that the decision-making power of the design is handed over to the Project Manager, does the design have components?

 

What is an architect?

We will not answer this question first. Let's take a look at some positions mentioned before the emergence of the architect concept.

Before the emergence of the architect concept, Microsoft was a model set up by the R & D institutions of most of our software companies. At that time, the popular positions were: Technical Manager + project manager.

Okay, of course there are also a lot of companies. Actually, the Technical Manager and Project Manager are individual people.

That is to say, most enterprises were responsible for developers, namely, technology + Team + project.

 

When we strip the "Project Manager" from development, and only remove the project progress and external obstacles for project promotion, in fact, the person in charge of the development technology and development team is the "Technical Manager.

 

Let me tell you that the so-called technical manager is actually an architect today, and we may all understand it more easily.

That's right. If the design of "architect" loses the right to speak, the right to make decisions in the technical direction, and the right to allocate development resources for team members, we can imagine that, how powerless this design is !!

 

Therefore, what is an architect?

An architect is a teamlear of a development team with technical say, direction decision-making power, and team development resource allocation right. It is also the program designer. Of course, he is the soul of this program team !!

 

Therefore, if you don't want to be a teamleader programmer, you can never become a real architect!

At the same time, it is not the architect of teamleader, but also an overhead, pale and powerless architect!

 

2. How can we think with the architect's thoughts?

 

Architect, assuming that it is simply to turn the requirement into a program, it is not an architect, it is called "Drawing Based on gourd ".

The architect assumes that he is only proficient in various frameworks, such as technologies such as S \ s \ H, and uses technologies such as S \ s \ h to describe users' requirements, it is called "draw images with S \ s \ H ".

 

OK. If you don't want to sell it to anyone, how can you think about it as a method that architects should think about?

 

First, do you want to call an architect for an undesigned architecture design?

This situation is too common in the software industry !!

Why is there no design?

Because many people do not know what design is !!

 

What is design? -- Design exists for the future! -- December June 2010

 

There is no future-oriented, but only the past. It is definitely not a design, but an imitation !!

Design exists for the future !!

 

That is, there is no design without innovation !!

That is, there is no design without changes !!

 

Think about your design with evolution !!

Let your design go beyond all theories !!

Design is just the carrier of memory, not the memory !!

In fact, programmers are artists, not construction workers !!

 

So why can't you become an architect?

Do not simply start from a technical point of view and work in the direction you take for granted. You must learn to think with design ideas and make yourself a weighty person !!

 

My weibo: http://weibo.com/useway

 

Bell, author of Java programmer, work

 

Thank you !!