preamble
I was recently asked by a small group of people on Planet Knowledge: how do I get up to speed quickly on a new project?
This question is a public one, and I'm guessing a lot of guys who have changed companies want to ask it.
I've changed jobs a few times over the years I've been working, taken over some of my coworkers' projects, and need to get up to speed on new projects of different types on a regular basis.
Today's post talks to you about some of my summaries and reflections, which I hope will be helpful to you.
1 Use of project functions
First of all, you need to use the functions related to the project, know what the project is doing, what are the main functions, have a general impression from the macro level, it is more unlikely to forget.
For example: your project is a mall system or a group buying system, think of yourself as an ordinary user and visit your system's APP or website to walk through the complete process.
You can familiarize yourself with the business quickly.
Then use a small notebook to record the main functional templates of the system to get a deeper impression.
2 Look at the project documentation
Look at the relevant documents in the project, the architecture diagram of the system, flow charts, etc., to have a certain understanding from the system level.
If the project has documentation, be sure to check it out more often.
It can help us to quickly familiarize ourselves with the program.
The documentation of the project is as important as the manual of the project and can help us to go through a lot less.
The Business Architecture Diagram allows us to know how the business modules of the project are divided, which are the public functions and which are the important ones.
The technology architecture diagram allows us to know the technology stack used by the project, the dependencies between services, the deployment of the project and some middleware.
Process mapping allows you to quickly familiarize yourself with business processes.
3 Viewing the calling interface
To the page function in the system, check the interface of the call.
The url address of the interface allows you to quickly find the relevant code in your project.
On which pages, in which business scenarios, which interfaces need to be called.
Figure out the core interfaces, and what code is in the core to make notes.
Input parameters and output parameters, roughly what they look like.
There is no unified package or specification.
4 Viewing the Table Structure
Look at the table structure of the database and sort out how the tables are related to each other and what the most core tables are.
We're just starting out, and there's no need to figure out all the table associations and fields at once.
This is easy to forget after a while.
I would suggest first familiarizing yourself with the table structure of the core function, the tables it is associated with, and what the main fields are.
You can use PowerDesginer to draw an ER diagram (database relationship schema diagram) between tables.
Clearer and more intuitive.
5 Try to fix the bugs
If you want to quickly familiarize yourself with the code in the project, you can start by fixing bugs, and have an entry point to quickly familiarize yourself with the related business and code.
By fixing the bugs, you can push yourself backwards to read the code in question, otherwise the bugs are not always resolved.
Of course bugs are graded:
- simpler
- moderate
- straitened circumstances
I'll start with simple bug fixes.
Running through the complete process of compiling, running and deploying a project will help you quickly familiarize yourself with the process of developing, compiling, running, testing and deploying a project in a company.
Then gradually start fixing medium and complex bugs.
The ability to continually boost confidence.
If you come up at the beginning and fix complex bugs, chances are you won't be able to solve the problem for a day, which will add to the frustration.
6 Drawing Flowcharts
I have used the features of the system before and have also read the source code of the project and modified the bugs.
Next, try to sort out the business for yourself and draw a flowchart of the processes involved.
We recommend using: and processon, two free online drawing tools to draw flowcharts.
When you are done drawing, it is automatically saved.
If there are other colleagues on the project team who are familiar with the project, send them to review it for you.
Being able to spot some problems in time and fix them immediately.
After a while, if you forget certain processes, you can come back to these flowcharts that can help us quickly refresh our memory.
7 Positioning problems on the line
Troubleshooting and localizing online issues helps to gain a deeper understanding of the business logic.
It is generally more appropriate to locate online issues after we have some familiarity with the business logic and code.
If you start locating urgent problems on the line on the first day of contact, it will probably be enough for you.
To locate online problems, you generally need to review logs, monitor and database data, and review relevant code to synthesize the information you have and troubleshoot the problem.
Locating problems on the line helps to gain experience in the project.
Helps in deeper understanding of business logic and code.
If you have some experience, you will be able to locate and solve the same problem very quickly.
8 Development of new requirements
With the previous steps, we have familiarized ourselves with the business process, table design, and related code.
Next, try developing more complex features.
Before developing, get the requirements document thoroughly clarified to avoid rework later and more time wasting.
If your company has a development specification, read it before you develop and write your code according to the specification set by your company.
If the company does not have a development specification, you can write the code in the same style as before.
If the previous code was written in a less elegant way, you can write a more standardized code according to your own specifications.
If you have reached this stage, it means that you are fully on board with the new project, already.
One final note (ask for attention, don't patronize me)
If this article is helpful to you, or if you are inspired, help scan the QR code below to pay attention to it, your support is my biggest motivation to keep writing.
Ask for a one-click trifecta: like, retweet, and watch at.
Concerned about the public number: [Su San said technology], in the public number reply: into the big factory, you can get free access to my recent organization of 100,000 words of the interview dictionary, a lot of partners rely on this dictionary to get a number of big factory offers.