New users enter new project development, new users enter project development

New users enter new project development, new users enter project development

I have changed three companies over the past few years. I often encounter a temporary addition to a project team for development. It is especially important to improve my work efficiency while understanding the business, because the project is always in the "catch up" status.

After several times of "getting ducks on shelves", I personally concluded that a fast development method may not be the most practical, but I personally think it is quite effective.

1. Familiar with business processes.

No matter how technical you are, what you make is of no value to the customer if you don't understand the business needs first and cannot make the results that the customer needs.

Do not think about developing and understanding business needs, which will greatly slow your development progress. In addition, if the business is not familiar with the development, even the simplest basic data maintenance will also cause repeated modifications due to unclear business restrictions.

2. Understand the Data Structure

After understanding the business process, first understand the data interaction between data tables for the development module that you are responsible for (when the rest of the time is sufficient, after each button is pressed, you must have a general understanding of which data tables will be affected.

3. "Imitation"

The first two steps are the foundation. "Imitation" is a good start when you are familiar with unfamiliar system framework development.

We recommend that you first find a simple basic data maintenance page for a single data table, track the code, and learn about the Basic Call of the add, delete, and modify method. It is best to develop a similar function module to further deepen your understanding of the system framework. The preliminary tasks of new recruits are generally not too complex. Therefore, the task can be completed as a supplement and the system framework can be understood. If you do not understand the problem, you must ask it. Otherwise, the problem will remain a problem and cannot be improved.

 

When a new person enters the project team, he must consciously follow the naming rules, file storage, and development methods of the project. If he keeps his original habits, it will disrupt the project and interfere with the development of other project members. Remember that a project result is not a single-person effort, but a result of team collaboration.