What is the most important thing during the probation period? Do the things that will help you get hired faster.
01
After completing the job-hopping, entering the new company does not mean that even if you actually join the company, the three-month probation period is officially started.
Especially in the Internet industry, in the probation period is left or take the initiative to leave the job everywhere, the middle reason is difficult to generalize.
However, most of the reason may be the company environment does not adapt, whether it is the development environment, or the work environment, or some kind of false pretenses of conflicting values.
This is why many people do not dare to move their house to the vicinity of the company for three months after job-hopping, because they are always afraid of getting back and forth in trouble. This should be a silent injury in the heart of most friends who are wandering abroad.
Life is such, fancy, you may not love but to face.
02
What thing should the programmer probation of Internet company do after all? In a word: a lot.
In the first week, I spent one day building the environment, one day getting familiar with the code structure, and three days looking at the business and part of the interface logic. This is the only arrangement of conscience company. Is it reasonable? Who knows.
Some companies do not speak martial arts, after the entry of a day directly dumped a small demand over, the name can quickly adapt to the business, said also quite serious.
Setting up the company’s development environment is a manual operation. Generally, in addition to the teaching environment setting up in the internship stage, we need to do things by ourselves when we join the new company.
After the environment is set up, it is a quick way to build the code locally and run it. There may be some special configurations that can be operated according to the environment documents, and then it is to get familiar with the various technical components, specifications and basic tools in the code.
No matter how the system is, new companies may encounter unfamiliar modules. For example, the technology stack developed by the company’s system is based on distribution, and some new technology components need to be learned. You can quickly familiarize yourself with official documents and project usage after work.
Pay special attention to these unfamiliar technical components, can say that they are not familiar but can not say that they can not, use the spare time to quickly make up, and then imitate the imitation of a ladle put on a look not difficult.
For most companies, familiarity with the environment and code structure is basically limited to two days, and then familiarity with the process of the existing product, which must be clear, familiar with the core business flow of the product.
With the help of business documents, requirements documents, and development environment, the process of clarifying the core business model, such as system foundation, authority management, and architecture, is not the most critical at present. Only by being familiar with the core process can we have a clear idea of the future requirements development.
03
Can give a week familiar with the environment and products of the company, visual absolute conscience, the second week will be involved in the development of version requirements, these years of work there is really no lack of many people in the first version of the cold.
The first version of requirement development is usually not difficult, which may be left over small requirements or small online bugs. This version is not used to test the upper limit of the ability of new staff, but basically depends on the working style, thinking, and the familiarity with the environment.
The basic routine of requirements development is nothing more than review, project approval, development, test and launch. However, this is a version that refuses to make mistakes. If the first requirement development fails or there is a major mistake, the probation period basically ends.
First: understand basic needs; At this time do not need to carry, unreasonable do not understand or do not understand, the version of the beginning of the discussion is clear, the most taboo to start to say very clear, at the end of the cycle found related problems or poor consideration lead to delay. This will lead to stress and time constraints, and efficacies will continue to appear, and then HR talks will occur.
Second: code and specification; The first step is to create a new branch, and then to complete the development of basic requirements. It is recommended to refer to the existing code style and logic at the beginning of the actual code development, without adding too much of your own habits and styles.
Third, good awareness; Business development really test the programmer’s consciousness, because the correlation between the business may not directly reflect on demand, only in advancing and debugging, new development after the biggest weaknesses than demand, cause some blind area problem, so in the advice business not familiar situation, through work overtime to catch development progress, Develop ahead of time so that you have time to deal with related issues if you find them, while making a good impression on the team and avoiding passivity.
If this requirement can be successfully completed and launched, it will basically be officially integrated into the new environment. There is no need for too much psychological pressure, and the subsequent version development and business familiarity will start to be in a good state.
04
Here to talk about the positioning of individuals in the team, how much ability to get how much money, we should assume the corresponding responsibility, this is the common consensus.
In a reasonable team with a good atmosphere, the division of labor is usually very reasonable. Senior engineers take charge of core business, junior engineers take charge of marginal business, and architects do daily architecture maintenance and upgrade.
Therefore, after I joined a team as a new person, I should clarify the department’s positioning on me and assume corresponding responsibilities. In the second half of the probation period, I will generally allocate development requirements of different difficulties according to my ability, and keep a good attitude and treat them seriously.
Another key issue is personal value. If it is a disadvantage to be unfamiliar with the current business as a newcomer, it is a personal advantage to be a newcomer who brings the accumulation and experience of the previous company, and personal value is how much influence and change it can bring to the current team.
Therefore, every job-hopper needs to know his strengths and weaknesses in mind, so it is important to apply what he has accumulated in previous jobs to the new company, such as developing specifications, usable components, business solutions, product iterations and so on.
Whether it’s professional skills or experience, it can help you quickly integrate into a new team and create value in a new environment. Only in this way can we pave the way for the subsequent development, which is the accumulation of advantages in job-hopping.
05
Finally, we will talk about a practical problem, how to face the transition to a regular job, usually from the work content, quantitative results, future planning three core aspects of the summary.
In fact, the real consideration is the work results during the probation period. The modules you are responsible for should match your salary level. If you have not made any major mistakes during the probation period and the development modules you undertake are difficult, you can basically pass the probation period.
People who can properly present their documentation in requirements development, such as development designs, process descriptions, interface documentation, etc., are generally more assured and trusted with their knowledge of accumulation.
Secondly, future planning. People with clear thinking and clear planning can undertake more difficult work, because they know what they want to do and know how to arrange and implement it. They should consider specific system problems or product rules to avoid false fireworks.
Finally, the appropriate rainbow fart to sprinkle a wave, such as reliable colleagues, good team atmosphere, leadership to take care of the company’s prospects, etc., do not go overboard and excessive, a few words to cover everything.
Last: workplace | 3 days to 5 days to interview, to move