Recently, a friend of mine asked me, “How did you become an architect over time?”

Today, this problem and everyone to share, with you!

Becoming an architect is every programmer’s goal, so how do you become an architect?

Definition & Level of architect

Junior Architect: Application Level, focuses on a single Application, has a very specific design product, and communication is limited to the development team.

Mid-level architect: Solution Level, who needs to focus on several applications to fulfill a business requirement, some high-level design, but most concrete design, communication across multiple development teams.

Senior Architect: Enterprise Level, focusing on multiple solutions. Design at this Level is more abstract and requires the solution architect and application architect to refine and communicate across the Enterprise organization.

One of the most important skills of an architect is “the glue that binds people across departments” : building Bridges between business people and developers; Build Bridges between developers and managers; Integrate different technologies and applications.

The architect’s day job

  • Identify the platform and technology for project or product development; (Technology selection, comparison, etc.)

  • Identify development standards and specifications: coding standards, tools, review processes, test methods, etc.

  • Design the system and make architectural design decisions based on requirements;

  • Document architectural design and decisions and communicate with the team;

  • Turn the design of high level into the design of low level;

  • Review and review architectural design and code, such as to see if identified patterns and code standards are being implemented correctly;

  • Collaborate with other architects and stakeholders;

  • Instructs developers in development

  • . (More architects daily welcome message added)

How to be?

Architecture is a challenging profession, and the breadth of knowledge often determines an architect’s architectural ability. Therefore, remember: read more, study more, think more, and ask yourself many questions when encountering problems. Then figure out why!

Architect, by no means overnight, is certainly through the time, project and so on hone, step on the pit, lie in the water, dry CURD, dry if-else type “boring” business development and so on, these are your future show off and ridicule for the topic. Don’t underestimate them, especially in the early days of your career, because they will help you grow in the future. Besides, how can you support your project without them? Anyway, don’t underestimate this.

When one day, you realize that some work content is boring, repetitive, but want to change it, it shows that you mature, grow up. At this point, I suggest you think a little bit about why you find these things boring and repetitive, and maybe you’ll find the answer:

  • It is my working way that is wrong. I work too orderly and mechanically. Can I improve my working efficiency?

You’ll find ways to improve your productivity, such as writing tools and optimizing your thinking. Let the usual 1 hour can finish things, in half an hour to finish, leave more time, but their own more thinking, more open the current code can be optimized and so on, more research on the realization of the product level, and so on, to understand why so achieve, why do not use other technologies or frameworks to achieve.

  • Look for changes in job content

Put forward the adjustment of the work content to the leader (the premise is that the current work has been completed very well), even if more work is ok, after all, this can attract the attention of the leader, more achievements, better development in the future.

Let yourself continue to improve, read more content, if you stay in this company for a long time, why not become an architect

  • Feel that their ability is good, the current growth space is limited, then job-hopping!

If you know something about the product you’re working on, it means you’ve got a lot of stuff, nothing new to get, and no room for growth, so move on.

Pick a company where you can learn something new and get mode again!

Be clear about the daily work of an architect, pay more attention to it, think about it and get involved in it, and keep training yourself to prepare for the future.

In addition, it is recommended that you continue to settle down and learn some skills outside of work, including in-depth study of previous technologies, new technologies/new areas of learning.

Now that you’ve done it, bide your time. Why is it so hard to be an architect?

conclusion

To be an architect, you need to be patient, learn, and broaden your horizons beyond your current project to focus on your company’s products, open source technology, and what’s going on in the hot tech community.