Why is your development so inefficient? - https://mp.weixin.qq.com/s?__biz=MzIwMzYwMTk1NA==&mid=2247484100&idx=1&sn=6d049494e35c19c5bd688d9d71f034d9&chksm=96cda389a1ba2a9f5425c4d4ad8ad8a91d5ba2ca1ed44871b345e411bf404a7ceb15e570595f&scene=21#wechat_redirect
in development, coding we have a layered architecture, design patterns as a routine to Efficient development, but you also know that coding is not all of development. A complete development process is summarized by object-oriented thinking, which is divided into OOA (object-oriented analysis), OOD (object-oriented design), and OOP (object-oriented programming). A good code structure requires requirement analysis and architecture design as an aid. Stay tries to describe an ideal and efficient workflow to you. With this routine, you can not only shorten the coding time, but also get the team's approval.
Regarding efficient development, the first reaction of most people is mature layered architecture, design patterns and third-party lib. These have given us design guidelines and convenient tools to implement requirements faster.
Efficient development also has another meaning. As for how a team can improve the overall development efficiency of the team, shorten the development cycle, and be able to iterate faster, step by step, you have to do a good job of demand analysis and architecture. the design of.
The senior development engineer will have a specific step:
1. Analyze the business process output model through OOA
2. Do object-oriented design based on the model OOD, and use UML to describe the overall process of a business requirement
3. Induction by OOD Use case diagrams, sequence diagrams, and class diagrams as blueprints to guide OOP
4. Design high-level abstractions to connect the entire business process in a pseudo-code manner
5. Split some independent tasks to other people for implementation
In the process of object-oriented programming, classic design patterns and design principles can also be applied to improve the stability of the system, making the code testable and extensible.
Compared with the junior and middle level, their focus is more on OOP, and on specific code implementation. In this way, it is not possible to have a complete view of the flow and boundaries of the overall business, and it is impossible to foresee the possible changes in demand in the future. Just doing some duplication of labor will not help to improve development efficiency.
Efficient development of Stay thinks that it should be divided into OOA, OOD, and OOP, which are the same as the one we just mentioned. First, there must be demand analysis, then process design, and finally the code implementation.
From OOA and OOD to high-level abstract architecture and low-level implementation, the responsibilities of different roles are different.
In addition to the need for continuous deepening of technology, future transfer management also requires abstract thinking, business capabilities, and communication and collaboration.
- 1. Working method:
2. Comparison of working methods:
3. Development process:
4. Positioning
