Quick integration into new teams

Starting a new job is not a big challenge, but I am still in this process. I will not talk about other things first, here, I will record some ideas about existing products after entering a new working group:

First, we may receive a series of project documents from PM, more or less. At present, there are many documents related to this project, because this is an outsourcing project, so, many documents and architecture-related stuff are provided from outside China, specifically to how many files, how many classes are required, what are their respective names, and what are their attributes, methods ...... This seems to be the architectural development that I often read in some books. It also uses the common three-tier architecture, namely Dal, BLL, and ui, but it is a little different, that is, Dal and BLL are closely related to data tables, while BLL operates databases in an object-oriented manner, that is to say, the Dal only provides a series of query, insert, update, and delete methods, and the corresponding entity classes are directly saved between the dal and BLL, instead, the involved fields are directly operated as internal members.

In addition, due to the mobility of the team members, the most urgent task for me to join the team is to quickly familiarize myself with the work of my colleagues who want to leave, so that he could smoothly take over the work left by him, so he immediately asked the partner about his work, including system engineering, files, pages, etc. After learning about this, the most important thing is to start from the most intuitive system process. First, log on to the test system, perform actual operations on common processes, pay attention to the pages and processes involved by the partner, and get some intuitive feelings, I also asked him about the business relationship and implementation logic of these pages and business processes. This process is still smooth, and the most important thing is understanding.

In the next step, you will get a rough review of many documents without looking at them very carefully, especially for requirements documents such as brd, as long as you can know the purpose of each document. Then, downloadSource codeDirectly observe the system architecture and call relationships between projects, and add some reference components that you are not particularly familiar with to the learning memorandum, based on an understanding of the overall architecture of the entire system and taking the task scope as the priority, we started to look at the relationship between the front-end, back-end services, and database access logic of these pages, mainly to view the specificCodeIn this case, I add some client controls, server controls, and special system calls that I have not used before to the learning memorandum.

The following describes how to get started with the new content recorded in the Learning memorandum, find information online, and check books to understand the purpose and usage of the content, and the actual code application can be digested, because it is a fast learning, so the depth of things, still need to be done again in the future work. After removing the obstacles to this knowledge, we still need to have a deep understanding of the content we need to be responsible for, so that we can understand the functions and hierarchies of the Code, because each person has the encoding style of each person, there is no need to make too much effort. However, for some team coding classes, we still need to make some records to ensure code consistency.

After completing the above work, your next plan is to try again to grasp the content you are responsible for and other business content from the overall perspective of the system. However, this requires a process, we need to continue to accumulate in our work. Of course, we also need to understand the database structure. At the same time, we need to call the stored procedures or database functions in the Dal, you can also directly execute SQL statements to identify the issue.

In general, I was confused at the beginning, because it was also the first job change, and the nature and content of my work have changed a lot. So how can I quickly adapt, it should be a big challenge, but if there is no challenge, there is no growth! Next we will list several steps that we think are important, hoping to help you:

(1) familiar with the company's office environment: including the team, office contact person, it contact person, etc.

(2) collect available resources in the team, including public servers, project documents, collaboration methods, and contact information.

(3) Understand your responsibilities: learn about your future work from PM, and give a brief overview of your project.

(4) Ask the "instructor" about the content and key points of his work, mainly to focus more on his work content.

(5) browse the shared files of the project team: mainly a series of documents related to the project, and understand the nature of these documents.

(6) log on to the test environment and familiarize yourself with the operation process: focus on the content you are responsible.

(7) Check the system source code and familiarize yourself with the hierarchical architecture: This mainly refers to the overall familiarity with the architecture and the overall structure of the database.

(8) Check the source code of some of the content you are responsible for, familiarize yourself with the specific application and call level relationships, database ing relationships, table structures, and other content: Take a detailed look, and summarize some team specifications.

(9) For some new technical content in 7 and 8, you need to quickly learn and master: to understand the specific application and simple examples.

(10) take over the responsible content and try to make some bug fixes and add new content: mainly maintenance.