The love-hate relationship between architects and programmers

       Recently at work, I found that we have different starting points between architects and programmers in many places. For example, some problems I encountered recently, many solutions, in the coding process, developers will use their own habits to solve problems method to deal with the problems encountered, and they will also say a lot of truth.

 

       In the background of our platform, some business data directly calls the RESTful interface of the third-party system.

 

       I found that someone directly constructs all the data we need to call RESTful in the background after the front-end js obtains the form data, not only constructs, but also fills in a lot of redundant data, constructing a large JSON data, or JSONArray, One attribute of all arrays is exactly the same as that of other elements, and basically 70% of the entire JSON data is completely repeated.

 

       The consequence of this is that every time the server is requested, basically 70% of the data on the network is redundant, and there is also the suspicion of doing business logic in front-end javascript.

 

       When I explain what I'm thinking, they all say, "I see what you mean, but what's wrong with me doing this?"

 

       In the end, he was willing to revise its implementation after three times of communication with us. On the one hand, he has basically realized the logical function of this part in his own way, and on the other hand, he did not have any specific implementation at all. Realize that you consider performance factors when doing each part of the function, and you can complete it.

 

       Sometimes the solution decided by an architect in a product is unwilling to be modified by others. One of the reasons is that he does not want his technical authority to be found by developers to have loopholes, and he also wants to ensure that his speech in the team has absolute authority.

 

       For developers, everyone is still in the stage of development and growth. In fact, the same is true for architects. They can improve their abilities in every aspect of their work, but everyone always means that this project is small and I only need to consider implementing the function, not considering performance.

 

       How do you communicate with each other when you encounter similar problems?

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326381891&siteId=291194637