Shulou(Shulou.com)06/03 Report--

Lesson 8 of "5 minutes from student to programmer"

After we enter the enterprise, the general leader will arrange for someone to take you, and some companies have "one-on-one" pairs of new employees to pay their respects. If the corporate culture is different, the way of leading new employees is also different. Some "masters" will teach you things and will take you very attentively; some "masters" will just take a formality, tell you the general situation of the project and let you read the code for yourself.

No matter which way he takes, you have to accept it, and even if he gives you a project to read the code for yourself, you should be grateful. Why? Because this is how he came over, when he first joined the profession, his master also taught him that he is what he is today, because he saw the code himself, so he thought it was the most effective way to let you look at the code.

Let's first deal with the emotions that the master may have on your cool side, so that we can better enter our career.

1. Paying more respects to the master is the best way to enter the profession quickly.

As mentioned earlier, some companies have the link of paying homage to teachers, which is a very good culture. I really hope that Internet companies all have this kind of culture. It goes a little too far. Let's get back to the subject. Why should we pay homage to the teacher? Master is half a father, who cares about you most, I believe everyone will say their parents, well, now there is half a father, in the enterprise, he is the person who cares about himself most.

In the enterprise, we will encounter three roles: master, boss and colleagues. Let's distinguish between these three roles.

The master will take up the responsibility of entering the profession and growing up. If you encounter problems, he will take the initiative to help you. If you do not grow up, he will be more anxious than you. Boss or eldest brother, this kind of person usually helps as much as he can, but he won't help you if it's inconvenient, let alone take the initiative to help you. Whether your colleagues are willing to help you read your mood. So in the enterprise, you should worship a few more masters, do not regard them as colleagues or bosses, so that your growth will be more guaranteed.

If I have been talking to you for a long time to pay more respects to my teacher, who should I worship as my teacher?

You have just entered the profession as a junior programmer, and your mentors are intermediate engineers. What they teach you is more about the realization of details, which is what you need to master and learn at this stage; you can also learn from senior engineers, but most of what they teach is methodology, which is not needed at this stage. You can use it to broaden your horizons and know the direction of growth. For those at a higher level, don't pay homage to the teacher, what they say sounds reasonable, but you can't fall to the ground and it's harmful to listen to it.

It is possible that the master's realm is not enough, cool you aside, what to do? All the content I said is my own initiative to take responsibility, their own initiative to grow, if you want, it all depends on your own. Therefore, in addition to the master, we should also have a set of ways to quickly enter the profession.

two。 The method of taking the initiative by oneself.

The master will tell you the project code, no matter whether he speaks well or not, detailed or simple, you should study hard. Each master tells a different process, so we won't discuss the process. But in the process of learning the project code, there are some goals that must be achieved.

1) understand the environment of the project so that you can run it.

2) the framework adopted by the project should be known, and the structure of the code should be clear.

3) the corresponding code of each module of the project should know where it is, especially the module that the master is responsible for. Points 2 and 3, as long as you know the general framework, you don't need to know the details.

4) to know how to add breakpoints, you can debug a function completely according to breakpoints. You need to know everything from functional entrances to business logic to the complete process of data storage. We need to know the details at this point, and the more detailed the better.

Before the master asks you to look at the code, you must achieve these goals. If you don't know how to do it, you must ask him, "Don't be embarrassed at this stage, and don't be afraid that others think you don't know anything." To achieve these goals, you basically get rid of all the problems related to the code framework, environment, and development tools, and then look at the code, basically familiar with business processes, code writing skills, and understanding of product functions.

3. Why do you grow faster than others when looking at the code?

Look at the common mistakes made by the code:

Generally speaking, the process of letting yourself look at the code will take a few weeks, and the time varies from company to company. So we need to make good use of this time.

Most new employees, when looking at the code, take a quick look at the code and forget about the front. After a few weeks, I felt like I had seen a lot, but I asked him that he didn't know anything. In fact, reading code can be boring, so most new employees will go to the forum at this stage, hoping to see the experience shared by others, learn development skills, and then feel much better. Now you are not even the porter of the code, to learn how to write code smoothly, the actual effect is very little.

Look at the code posture correctly:

It is better to see more than to look at essence. The third goal in front, let you know the module that the master is responsible for, will come in handy here. You just look at the module that the master is in charge of. If you can't understand it, ask him if you don't understand it, so that his knowledge will imperceptibly come to you, and the master is very happy. This apprentice is good. He adores me so much. Look at my code.

The above paragraph is a joke. The real advantage of looking at the master's code is: if you look at other people's code, the master may not have seen it, so he can't guide it. He is basically familiar with his own code. He doesn't need to spend too much time to help you. Engineers are very busy, he can't spend a lot of time on you.

4. The crooked way of the rapid growth of development ability

If you feel confident by the third point, take the initiative to ask the master for bug change. If the master gives you a bug change, don't read the latter part. If you are not sure, maybe the master still shows you the code, and you have read all the master's code, or you are tired of reading the code. Many people will be very lost in this link, the code can not be read, and there is nothing to do, the master also let you look at the code, and then have negative emotions, and then get drunk and dream to death on the Internet, which is not good for your career.

As people who have professional requirements, we need to take responsibility for our career growth.

Here to share a method, the information and code of the project are put on svn or git, you can go to see the code written by the master every day, there are records on the code management tools, and then write the code written by the master every day, no matter whether you understand it or not, right or not, so that you know how to do the function, how the master thinks, how to understand the function, and you imitate a few functions, and you will know all about it.

In this way, in less than three months, there will be 70 or 80% of the master's skills.

5. Summary

The master leads into the door, and the practice depends on the individual. This lesson to share with you, how to learn from the master, quickly adapt to their own position, take the initiative to grow in the position, improve their coding ability.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.