Next, I plan to update a few entry-related articles. The reason why I wrote a series, I feel that there are many things in the entry that are worthy of in-depth thinking and summary. The next few articles are not thoughts before entering the job, but after entering the job, when I look back, I find that I have taken a lot of pits and detours, so I plan to take the pits I have gone through during the time I just entered the job and some of the experience I summarized. Share with everyone.
Today’s article is the first in the onboarding series. I would like to talk to you about how to quickly become familiar with the work environment in the shortest possible time when joining a company. The so-called working environment here includes aspects such as business, technology and team.
1、
Before joining a company, you must have known some information about the company, such as what field the company does, and what are the general business and technology? And the development prospects of the team and the company.
After I interviewed some companies, the interviewer will basically tell you the general situation of the company as long as the questioning part does not involve company secrets. When you actually join a company, you find that there are many things you need to be familiar with in a short time, and then you can quickly integrate into the work.
According to my own summary ideas, I mainly divided into three major points, business, technology, and team.
2、
In terms of business, this is a very important and complex aspect. Some companies have simple business operations, but some companies have iterated to many versions, so it is not so easy to understand. Especially when it comes to areas that you don’t know, let’s not talk about a lot of technical terms, just say that the entire business line is enough for you.
I deeply feel that the company is mainly engaged in the financial field. In terms of understanding the business, many of the company's products do not know how to provide value to users. After all, I have not contacted before, so I did not do my homework in the early stage, which led to the later development. The self-developed function looks dumbfounded.
So when I am familiar with the business, I have summarized a few points for everyone.
* What is the company's main business?
Undoubtedly, what a business does depends mainly on what kind of users it provides.
* What problem does the company's products solve for users?
What products and tools does the company have that help users solve those problems?
* What are the specific procedures of the company's business?
Find out who is involved in a project from business personnel to development to final delivery, such as product managers, project managers, business personnel, and developers. This is mainly for future problems and know to ask the corresponding colleagues in charge.
* What products does the company have and how are they used?
It is not enough to only know what the products are. The most important thing is to experience the products developed by the company and how to use them. This is conducive to the later development and experience of our developers.
In the beginning, it was impossible to understand all lines of business, so it was OK to have a general understanding in mind.
3、
In terms of technology, the first thing is to understand the company's internal technology stack, such as Python or JAVA in the back-end, and Vue or React in the front-end.
In addition, understand the basic structure and modules of the company's project, such as whether there is a component library, how the component library is introduced and used, and what the specification is; another example is the front-end and back-end cooperation interface documents. If the back-end data has not been released, how to mock the front-end data.
Then there is the specific development process and specifications, which is also important to us to understand, what are the version tools used and the submission specifications. And what tools are used to synchronize bugs before testing and development, and how to synchronize. And the specification of the front-end UI design drawing and the use address of some icon libraries.
In addition to the above, there are several points. You must figure out the directory structure of a project you participate in. If the system is divided into modules or hierarchical, you generally know what functions each module is used to achieve, such as what I do now There are plug-ins in the project. These are all how to carry out configuration management. It is necessary to clarify these, which are all in preparation for the next development.
4、
As for the team, I am deeply impressed by the team.
A person is awesome, not as good as a group of people. Sometimes we see a lot of introverted developers or some skilled people who are not good at supporting developers and often fail to integrate into the team. In the end, whether it is communication or communication, there will be a barrier and the atmosphere of the entire team. It was very depressing.
Someone may just say that I may be due to my personality. Some habits and personalities are just not suitable for working with others. Indeed, many times, due to many personal reasons, it is not suitable to be integrated into the team at the beginning. After all, the environment is new and the members of the team have just met for a while, so it is more about running in and understanding.
In addition, there are many design solutions in the project that are not decided by one person, but the best solution obtained through joint discussions among team members.
summary
Today, I mainly summarized from three aspects: business, technology, and team, how to start quickly and adapt to the new working environment when I first started.
Business is very important. It determines who you want to use and what value it generates. Technology, housekeeping skills, each company's technical system is different, but how to get familiar with the project, starting from the above aspects, there is no big problem. Team, a team, the most important thing is the ability to cooperate. Don't be separated by the team for personal reasons.