The theme

First of all, I sincerely welcome your arrival!

This is not a polite remark, because you will be participating in our project, sharing tasks and contributing to the team.

So you have to understand that if you’re going to have a hard time working in a team for a while, it must be the subject that’s doing it wrong.

This is my sole purpose in writing this article, hoping that you can give you a way to be welcomed by everyone on your team.

Be familiar with the project

First of all, you need to be familiar with what our team’s project does and what its value to the whole industry is. Then you need to understand the technology stack, project structure and code specification of our whole project.

Code specification

The code specification is important, so important that if the code specification is widely broken, you can be held accountable by everyone on the team.

The same code specification is easy to follow, and you just need to adapt to the project specification for a while.

And that’s what you have to do.

Project technology stack

The technology stack that will be used for the project should be introduced to you during the interview and you will be asked to join the team if the right person feels like it.

If there is a stack you don’t know about, take the time to learn about it, because it is the most fundamental problem you will encounter in your project.

The project architecture

For the architecture in the project, you are expected to make a project architecture diagram according to your own understanding. The same is required of any newcomer, good or bad.

Mentors can’t be sure that you can fully accept and perform tasks without being sure that you understand the overall structure and flow of events in the project.

If in the process of understanding, you come across something that feels unreasonable, something that you can’t understand. Don’t be in a hurry to question it, anything that exists is reasonable.

Of course, if there is a problem with the architecture, that doesn’t mean you can’t question it, but you should tell your mentor that you understand what you are doing to solve the problem. And with that in mind, I have a better solution, what are the benefits of doing that than before? In this way, your advice will be reasonable, effective, and problem-solvable in the tutor’s eyes.

In the past work experience, there are many places where the new staff will put forward their own ideas, which are reasonable, and some points are really beneficial to the project.

One rule: Talk about problems, complain less.

If there are problems with the project architecture, speak directly about the problems you have identified and your recommendations. Complaints like the following are totally unnecessary because they don’t solve anything:

• Running is stuck
• Unclear document
• Long compilation time
• There was a problem with the project event call flow and confusion

What mentors like to hear more is:

• Where do I find a performance problem, in which file
• The location description of the call at a certain time was not clear enough, I made some documentation after analysis
• The overall compilation speed in the project was slow. I analyzed that a package could be precompiled to improve the compilation speed

Project process

Another important thing you need to understand is the overall project process. Different companies have their own project release process and task management.

How to receive project requirements, schedule, test, release. The whole process requires you to have a general understanding.

This will ensure that you know exactly where you are in the process of working and will help you get into the rhythm of the company quickly.

task

Task scheduling

As a newcomer, the first assignment you receive is often challenging, and your mentor expects you to manage your schedule properly.

In order to ensure that the task is completed on time, some time for technical difficulties, some time for communication and some time for scheme design should be taken into account in the task scheduling.

Every assignment your mentor wants you to take on, you know what you’re doing. And have a certain sense of responsibility and responsibility for their own tasks. If you find that there are technical difficulties in the project that are difficult to overcome and the risk of overdue, be sure to inform your supervisor in advance, do not feel that the supervisor will blame you for this. Because mentors are mentally prepared when they assign you tasks.

It is far better to be honest about the status of a task than to find out that it cannot be completed when it is due.

Technical difficulties

In general, some of the tasks assigned to you will not have major technical difficulties, and if any will be solved. The tutor expects you to fully understand the existing solutions in the project when faced with technical difficulties.

This is a very good opportunity for you to have a deep understanding of some key issues in the project. If you are not clear about the technical difficulties, the tutor expects you to bring your own ideas and technical points to the tutor.

Afterwards, you should record your thinking process in detail and summarize your solutions. Only in this way can you grow quickly and increase your influence in the company.

Ask questions

attitude

Maybe you’re from BAT, maybe you’re from 985, maybe you really despise your mentor. However, at the moment of asking questions, it is not a good habit to listen quietly to what the tutor says and interrupt others eagerly.

I can understand that for every programmer, the better the programmer is, the more he has his own ideas and opinions, but this is also the biggest weakness of programmers.

If you are unhappy with your company, find the right person to address it, such as HR.

You don’t get paid to share your salary with your mentor. You owe it to your mentor to explain things to you selflessly.

Ask what

Returning to the subject of this article, I sincerely welcome you as you are about to take on some responsibilities for the team. If you’re adding to the team’s workload, you need to take a look at yourself.

Think about a question before you ask it. Figure out if you can solve the problem first, such as:

• How did this place go wrong
• What is the lifecycle in VUE

Like this kind of debugging or Baidu can solve the problem, ask the tutor will only make the tutor unhappy.

Then think about the problem and ask your mentor if they can solve it, such as:

• Computer card, computer can not access the Internet
• How and what should the button display

To be clear, mentors are there to take you on the road, not to test you.

A company is not a school. A task is not homework.

When a task is assigned to you, the mentor can only give you the general direction of how to complete the task, and the specific implementation details need to be completed by yourself.

Don’t ask your mentor how to take a step. Because it’s better to do it yourself.

Cost performance

Be aware that every minute of your mentor’s time is worth more to the team than every minute of yours.

Treat every question as a transaction.

Ask valuable questions and learn to think for yourself. Is the ultimate moral of growth