On the Relationship between design, demand, and coding

The design itself must also have a "Source". The design that appears out of thin air is just a fantasy and does not meet the actual needs. no design can satisfy all requirements. Therefore, the design must be based on the "requirement" source.

First, there is a demand first
Here we will talk about what needs are. In general, the demand is the business. Your understanding of the business is a process that is constantly deepened. This process is not designed, but your insights, experiences, and associations, compare other products to find inspiration. in summary, analysis, comparison, and data collection.

Demand is neither a design nor a code. Demand is the source of everything (except your desire to make money), but demand is not opposed to coding. A certain amount of encoding should be generated. as a programmer, we have two languages: a mother tongue and a programming language. we use our native language and programming language to think, but this kind of thinking is not to get the actual product, but to verify our ideas, it is a test. is a tool.

Second, design in the middle.
When we have a deep understanding of the business and can pass preliminary verification of the program, we need to design it to help us carry out the "orderly" work. the purpose of the design is "order", which is methodical, not creative. creativity is the demand stage, and design is the engineering stage. if you want your code to be well organized, it will not be messy, and you can easily start your work, you need to design it. like a building, you can build it at will, but when you build the second floor, you find that the first floor is missing a pillar, or. when a wall is built, a wall cabinet needs to be placed and pushed down. the purpose of the design is to let you first see the overall, do a good job of reservation.

The design stage is the stage of the overall architecture software, the stage for organizing our understanding of the business, and the stage for decomposing each process. We must be able to solve any process, wall-built workers, gray-and gray-painted workers, break down into processes that we can solve, find out the processes that we cannot solve, and modify requirements.

Designers often want to design a design that is beyond their needs, hoping that the design can meet future demand changes. this is wrong, at least at this stage. if you want to meet your future needs, you should increase your needs in the demand phase, rather than thinking about changes in the design phase.

Third, encoding
It is very easy to build a house with drawings. if all the skills required for coding have been completely solved in the drawings, and all the procedures have been done before, then according to the drawings, we will inevitably get the results presented by the drawings.

 

Conclusion: Do not rush to design, do not fear coding, extend the demand analysis stage, and make yourself think about it for a while.

Design is not a good solution to all problems, but an engineering instruction. The idea of true creativity is given at the stage of our needs.

Do not design ahead of schedule, but make demands ahead of schedule.

Sort out our coding snippets to provide design materials. The design is a language higher than the encoding. The material of this language comes from programming experience.