In short, that’s because you lack the basic theoretical knowledge of architecture. I recommend a nine-part series on the basics of architecture.

Architects are a special breed, especially in the software industry; Being an architect is also a desirable job. In the software industry, architects and engineers are like Gods, creating a variety of software products to serve humanity. To play this role, architects naturally need to have some kind of God’s perspective to see and express the world. The software created in this way can grow up and keep pace with The Times, in order to better meet human needs.

Engaged in the software industry for some years, from this industry to learn a lot, also harvested a lot. I’ve always been acquisitive, always thought I should do something for the industry. During the Spring Festival of 2016, I will dedicate my thoughts and summaries of so many years to the readers in a series of articles. I hope these articles have been inspiring and thought-provoking, making a small difference in understanding architecture, designing architecture, and writing good code.

Download the way

PDF version: Click the link at the bottom of this article to read the original article.

EPub version: Pay attention to chat about architecture wechat, reply keywords “chat about architecture” can be downloaded.

MOBI version: pay attention to chat about architecture wechat, reply keywords “talk about architecture” can be downloaded.

Baidu reading version: pay attention to chat about the architecture wechat signal, reply keywords “architecture chat” can be downloaded.

directory

Architecture Ramble 1: What is Architecture?

There has always been a lot of debate in the software industry about what architecture is, and everyone has their own understanding of it. Many architects start talking about application architecture, hardware architecture, data architecture, and so on. I’ve looked around for a definition of architecture, asked a lot of people, and found that there is no universally agreed upon definition.

Conceptual understanding is the foundation of understanding architecture

This is the second part of the ramble architecture column. The author discusses the misunderstanding of concepts, how to effectively understand concepts, understand the meaning behind concepts, and how to use the understanding of concepts to learn quickly through several examples. Mastering these principles helps us to quickly identify and locate problems during the architecture phase.

Architectural Ramble (3) : How to identify architectures

According to the previous definition of architecture, the first thing you need to do to build a good architecture is to identify the problems that need to be solved. In general, if the real problem is identified, then 80% of the problem is solved. This ability basically determines the level of the architect. So what are the difficulties of facing the problem?

Discussion on Architecture (4) : How to do architecture segmentation well

This is the fourth installment of my rambling architecture column, in which the author introduces sharding of architecture and points out the essence of sharding is the alignment of benefits. In this paper, the author will discuss why shard is needed, the principles of shard, shard and modeling, shard output, organizational structure and other issues.

Architecture Ramble # 5: What is Software

This is the fifth part of my ramble on Architecture column, in which the author will once again reflect on what software is from the perspective of his own cognition. In this article, the author discusses the root causes of the popularity of software and the role that software plays.

Architectural Ramble (6) : What problem is software Architecture trying to solve?

In this sixth installment of his ramble on Architecture column, Kevin continues his discussion of why software architecture exists, and then goes on to explain what it is. It fits perfectly with the why-how-What idea that’s been going viral online lately.

Discussion on architecture (7) : Architects have no right to speak, so what’s the point?

In this seventh installment of his rambling Architecture column, Kevin discusses what an architect is, what it takes to become an architect, how to discover “whose problem is it,” and the rights and obligations of an architect. Just as the author said, an architect must be the leader of an organization and have the right to mobilize the structure of the organization, so that the role of the architect can be better played and the adjustment of interests can be better implemented.

Architecture: How to write good code from an architecture perspective

In this article, the eighth in his rambling Architecture column, Author Kevin gives examples of how to write good code. When we have a good architecture, we need to think about how to put it on the ground, and that’s when the code becomes very important! Never let code become a bottleneck for architectural extension. The author mentions code architecture, so read on.

Do you understand the relationship between technology, business, and architecture?

In this ninth installment of his rambling Architecture column, Kevin takes a closer look at the relationship between technology, business, and architecture. Just as the author says, technology always comes into being when human beings are solving ever-increasing demands on business for the purpose of obtaining greater and better benefits.