Design first, coding later.

That night, my wife talked to me about the tools to be designed. I didn't think clearly about many things, couldn't write code, and didn't have a strong sense of direction, so we spent some time sorting out the design points on paper (please ignore this advertising paper).

Because I know that if I don't figure this out tonight, it's hard to see a movie.

So it took me some time to think about and write this article, and I could read it in a few minutes.

Design first

In real life, when most developers hand over the building with decoration, the owners ask for the design drawings before they can know the layout of water and electricity, which is understandable; for the whole community, it is first presented on the design plan, not that construction workers build what they think of, and must do it in accordance with the requirements of the design drawings, otherwise arbitrariness may bring disasters.

So, what are the requirements of software development in software engineering?

Software development must go through four steps: preliminary design, detailed design, coding and testing. This is the wisdom of software engineering.

If you do not follow these steps to carry out software development, it is not software development under the guidance of software engineering, but just manual workshop "writing code".

Two programming routines

There are two common routines of programming development:

When I first joined the industry more than a decade ago, I was developing and designing, and I was not satisfied with the results. It took me about a year to realize the importance of design first. I always have a stronger sense of direction to think about what to do than not to know what to do.

Design first, have confidence in the overall framework, even if the direction changes, also have the confidence to embrace change, make some fine-tuning, and even avoid the introduction of design complexity, you can diverge to think about many points, but you have to get it back in the end. consider resource factors (time, labor costs, etc.), first implement a simple, clear, measurable framework, just describe it clearly Even if you first use the TDD mode to verify whether it is right or wrong.

Of course, a responsible engineer is quite reliable and important, better than I know how to do it.

By essay, unsorted