Ah, I finally wrote the code for accessing the data of a single data model.

After a month of continuous development, the design of N re-modifications will finally be well targeted at the access to a single table, haha, so happy. if I have met my needs, I have to take a further look at it in the use process. the support for many-to-many relationships and the generation of data tables will be rewritten later as needed.
After this development, I fully understand the unique charm of unit testing. When I first passed all tests, it was still a chaotic design with poor structure and unclear class responsibilities. After the compilation, after about three days of redesign, add a new class and modify the name of the unsuitable class. Haha. I finally completed a design that I still think is good. Without the unit tests I wrote earlier, I think this job is unimaginable.
At the same time, I also had a confidence improvement in my own design capabilities. I realized that I could make a one-time design only when I knew something very well, there is an initial idea on the paper. There is no need to design the content on the paper before development. initial Design and final CodeIt can be said that there may be none in terms of model design. Haha, it seems that this is a practical path for agile development.
Haha, I'm so happy. I'm playing a game first.