Recent thoughts essay

1. The structure will not disappear
  and will not disappear, either displayed or hard-coded in the code.

2. Basic code quality standards
  : can be clearly and completely considered.
        Easy to modify. It is necessary to follow the basic ideas of programming for interfaces and avoid content coupling.
        For example:
        mixed dto is used as a method parameter, and it is difficult to debug the parameter. Not sure what dto properties are useful.

3. Web mvc action minimizes non-interface related logic.
  Control is the interface's control of the model, not the business logic control.
  Actions are adapters for interfaces and models.
 
  For a deeper understanding of adapters, see the description of Dao in "j2ee Core Design Patterns".

4. ProcessTaskGroup.hbm.xml can't find the error, but the ProcessTaskGroup.hbm.xml file exists, it is estimated that the location of the file is wrong.

5. There is an intermediate temporary model between view-model.
In one case, the temporary model is the editorial data model, which is a partial copy of the software model.
Another case, the data model of the control itself on the web interface.


6. For Service reuse, on the one hand, it means that the same method can be reused. It also means that when the interface changes, the originally implemented Service functions can be reused.

7. Hard-coding always exists, either hard-coded type or hard-coded value.

8. The interactive design itself is not difficult, and ordinary people can complete part of it. The biggest problem is getting it right. For example: a table is misused where a tree is needed. The content that should be laid out in one interface is split into multiple interfaces, etc. Possibly, people who don't know how to design have no direction, and they will go on when they catch an idea, thus wasting a lot of time. Therefore, existing ideas, do not expect to be found automatically, need directional communication.
In addition, there is no way to deal with the details. The quality can only be guaranteed by means of re-examination. For example, in a selection dialog box, where the OK and Cancel buttons should be placed, the designer should save it, but not the Cancel button, and ask: If there is a difference on the top, the window can be closed. Questions like this can only be re-examined.

9. The usual call form of a singleton is xxx.getIntance().xxx(), so that the method call has no mandatory dependency on the type of the return value.
It doesn't make much sense. Mainly, the singleton can be used directly. There is no need to add intermediate variables and add an intermediate link.

10. Timing diagrams depict key design points. To be precise, it solves the problem of distribution of responsibilities during operation. rather than extraneous details. For example, when there are multiple levels of inner method nesting, it may be describing the details of irrelevant responsibilities.

11.as400 cl abbreviation http://m.03964.com/read/f500eaaa2250dc69b4d31696.html

12.mvc is a special object relationship, view uses model data for one-way coupling. In general, OO data is distributed in various objects, and the use relationship of data is meshed. How to couple objects needs to be designed under the design theory.

13. Get what you need.

14. Sequence diagrams are executable.

15. Program customer data is also customer data. It has the property of being glued to the program, which leads to a program that cannot be used universally.

16. There are obvious differences between program client data and optional functions. The former main program does not depend on specific program data. In the latter case, the main program is aware of program data.

17. The sequence diagram reflects the operation process of the upper "interface layer" of the specific code. This layer directly reflects the business logic.
    Some people don’t think hierarchically (more fundamentally, they don’t know how to program for interfaces, so code layering is impossible. For example: the string concatenation form of the key of the map in the method, which is defined as a parameter and passed when calling) Naturally they don’t like it Use timing diagrams. Because the sequence diagram forces the programmer to think at the interface level of the class.
    This layered ability of sequence diagrams and the ability to correspond to business on this basis is amazing.

18. The corresponding fields of the hibernate value object cannot be like

19. The representation of the method name can either directly represent the business, or it can be a function plus parameters to complete the business.
    degradeWarningInfoLevelTo1(wiid);
    setWarningInfoLevel(wiid,1);
   
    should make the interface as generic as possible on the basis of ensuring that the business process can be seen from the code.