Hello everyone, this is Liang Xu.
For newcomers in the workplace, especially fresh graduates, after they get an offer, they will feel anxious for a while after entering the company. For example, if you don't understand the company's project development process, you don't understand the code, you don't know the business process, you don't know the framework, and there are various problems.
So many people at the beginning are worried about whether they can be qualified for this position or whether they will not even pass the probation period. In fact, this mentality is very common, and every programmer should go through such a process.
Take myself as an example. Since I was self-taught and transferred, my skills are a bit worse than those who came from major classes, so I was really anxious all day when I became a programmer. . During that time, I often had nightmares. I dreamed that my trial period would not expire, I was fired from the company, and I dreamed that I couldn't write my code, and I was rejected by the leader. I even woke up in a dream several times. You must know that my sleep quality has always been very good, and it can wake me up in my sleep, which shows how much anxiety I feel.
So if you are as anxious as I am, don't worry, this is a necessary process. First of all, you have to adjust your mentality, because you have passed the interview after all, at least it means that your level and ability have been affirmed by the interviewer, so you don't have to worry about your own conditions. Being able to get an offer already shows that you are qualified for this position .
Then, when you first enter the company, the leader generally won't arrange important things for you, or give you a very important task all at once. If you are a person who provokes important tasks from the beginning, I believe you will not have time to watch this video of me.
Generally speaking, a few days before entering the company, there is not much to do. The most important thing is to go through the entry-related procedures, and then install the required working environment on your computer. For example, install some code editors, compilers, tools, software, drivers, etc. that you need in your work. Then, the code of the project you will take over will be cloned to your computer.
After the environment is set up, the leader will send you the relevant documents of the project, and then let you familiarize yourself with the code. Then, the leader will assign you a few simple bugs for you to solve. At this time, you start to really slowly enter the working state.
After entering the working state, I will provide you with a few suggestions so that you can quickly get out of the novice village and slowly become a cooperative programmer.
First, let the project code run
The company will copy the source code of the project to you. At the beginning, you should not make any changes. Try to compile the code first, and then let the code run. Don't underestimate this step. Different project compilation methods may be different. Even if the code is given to you, you probably don't know how to make the code compile. Even if the compilation passes, you probably don't know how to make the code run. Like the embedded project I did before, the code was compiled with Yocto, and the configuration of the compilation alone has made me feel bad for several days.
Then, use the shortest time to familiarize yourself with the company's project framework and business processes.
In fact, when your code runs, you already know what the project looks like. At this time, you can roughly know the framework and process of this project by combining the requirements documents provided by the company and comparing it with the running program. Of course, this process does not mean that it can be completed in one or two days, but to be familiar with the general framework and process first. Don't go too far with the specific details. The details need to be gradually familiarized in subsequent work.
Third, understand the technology commonly used by the company
Every programmer position needs to master many technologies, but not all technologies will be used in work. You need to master the most commonly used technologies in the company within a short period of time, and then slowly study and research other technologies. For example, for the embedded field, you may need to understand the use of the wifi module, how to programmatically turn on/off wifi, how to search for nearby hotspots, and how to set the AP/STA mode. For the Bluetooth module, you have to learn how to search for pairing and how to transfer data. Different positions have different technical requirements, and you need to study the technologies you need to use.
Fourth, keep learning
There are a lot of technologies that programmers have to learn, especially in the Internet industry. The technology upgrades are really endless. A new framework and new model will come out at every turn. So you have to maintain a studious attitude and keep up with the times. , Learn more about new technologies and new frameworks. You may not be able to use some technologies now, but you may use them when you change jobs later. Therefore, it is always good for you to learn more techniques without pressing your body.
Fifth, understand the needs
Generally speaking, the company already has a relatively complete code, you only need to add some more requirements on it. It is impossible for you to develop a project from scratch, especially for new employees. This kind of work is usually done by old employees. So for the understanding of requirements, you need to go to the product manager. As you all know, programmers and product managers are rivals. At this time, let's lower our stance and ask them for advice. There are many opportunities to follow them. As the saying goes, know yourself and the enemy, never slack in every battle. We let them first, and then slowly settle accounts with them later. Of course, this is a joke. People from the same company must live in harmony. After all, unity is strength.
Sixth, hold the thigh
There will be more or less old employees in the company. You must have a good relationship with them. If you have anything to do, invite them to eat, drink and drink. The so-called cannibalism and short staff. After you have a good relationship with the old employees, what problems do you have If it is, it is easier to consult them. It may take a day and a half to figure out a problem for yourself, but if you let the old employees look at it, it may be solved in a few minutes. Therefore, holding the thighs of older employees is definitely the best way to grow quickly. But then again, don't rely too much on old employees. If you encounter problems, you must first try to solve them yourself. If you have no clue, then go to the old employees. And even if they help you solve it, you have to reflect on it. How did they locate the problem? How do they debug? How did they solve the problem. Only by doing this can you make progress and technology can be improved.
Seventh, communicate with leaders correctly
Sometimes the tasks assigned by the leader or the requirements given cannot be completed or are difficult to complete. At this time, don't delay by yourself, and must take the initiative to communicate with the leader. But you must pay attention when you go to the leader. You have to think of several plans before you go to the leader to communicate. The company prefers employees who have independent ideas and can solve problems, rather than employees who seek leadership when they encounter problems. The company invites you to solve problems, not to ask questions of leaders. The stronger the ability to solve problems by oneself, the more important it will be from the leadership and the easier it will be to get promoted.
Well, the above are my 7 suggestions for novice programmers. I hope my friends can grow up quickly and get out of the novice village as soon as possible.
Finally, recently many friends asked me for the Linux learning roadmap , so based on my experience, I spent a month staying up late in my spare time and compiled an e-book. Whether you are in an interview or self-improvement, I believe it will help you! The directory is as follows:
Give it to everyone for free, just ask you to give me a thumbs up!
Ebook | Linux development learning roadmap
I also hope that some friends can join me to make this e-book more perfect!
Gain? I hope the old irons will have a three-strike combo so that more people can read this article
Recommended reading: