1. Before you start writing a program, you should carefully specify its appearance and its actions. 2. First design the visual appearance of the program. 3. If some objects are similar, consider combining them into a single class. 4. When performing the GUI design, you should design from the downward. To combine the Widget into a container, the container is combined into a larger container, and it is pushed. 5. If you browse from the head to the tail, you have to click the scroll bar, then this method may be too long, and there is a bit of trouble when you first understand, you should consider separating some of the code. 6. If a class or method is not fully needed at a certain stage of the design process, then you can write it into stub (root). 7. If some actions are found to be executed as a unit, these actions are placed in a method, and these actions are performed by calling methods. 8. When designing other people who have possible use, try to predict what other programmers want to get. 9. Like the class that makes the visual design decisions, let the class decide how to use the method, and the method often inspires the variables they need. 10. If the two program blocks are found, it is necessary to consider packing them into methods. If it is a method, it is necessary to consider whether to call another method in one method. 11. Once the program runs satisfactorily, look back to check the code carefully, the code is clear? Is it proper? Can I improve? Can you organize? Edit, edit! !
