Bug-driven development)

To be honest, as a domino developer, methodology is a high-level methodology for software development such as test-driven development and feature-driven development ), only occasionally I have seen and heard of articles and programmers developed in other languages. Domino's unique architecture makes these methodologies unsuitable. However, based on my recent experiences with a large foreign Java product (I also learned from my friends in the chat), No matter what language the project is developed in reality, there is a general methodology, which has not been paid much attention by theoretical practitioners and has been systematically summarized and proposed.

I'm going to name this method bug-driven development ). Although the name is the same, programmers are familiar with it. Simply put, it is to discover bugs-eliminate bugs-and discover new bugs. Such a continuous loop process drives development, which is called bug-driven development. To use this methodology is very simple, you only need to do one of the following:

• Select beginners or programmers who have no experience in software system architecture and design principles to develop complex systems.
• Project boundaries are unclear and demand changes frequently.
• Insufficient manpower and time constraints.
• Lack of resources or attention, without (adequate) testing.
• The product manager is eager to launch the new version, and the Project Manager makes the project online in a rush.

Bug-driven development, simple to learn, easy to implement, and widely used. Today I first put forward it as a methodology and hope to share it with colleagues, to better promote the research and development of this method.

Bug-driven development)