"5 minutes from the student to the programmer" Lesson 8
After we entered the business, general leadership will arrange for someone to take you, there are some companies "one to one" twinning coach new employees. Different corporate culture, leading the way to new employees is also different. Some of the "master" will teach you something that will be very hard with you; some of the "master" is just a formality, to tell you the project under the general situation, let look at the code yourself.
No matter which way he used, you have to accept, even if he gives you a project to make yourself look at the code, you have to be thankful. why? Because he is so over, started going to row, his teacher taught him the same way, he can have today, his own look at the code to see, so let you look at the code, is the most effective way he thinks.
We first master emotions cool while you will probably generated to handle it, so that we can better access career.
1. Multi thanks to the master, is the best way to quickly entrants
Like said earlier, there are some aspects of the company's apprentice, this is a very good culture, I really hope that Internet companies have this culture. Pull away a bit, we come back to the subject, why want to coach? Master is half father, who most care about you, I believe we will say that their parents, well, now more than half a father, in the enterprise, he is most concerned about their own people.
In business, we encounter three roles: teacher, boss and colleagues, we have to distinguish between these three roles.
Master will take up their own entry, responsibilities grow, you have a problem, he will take the initiative to help you, you do not grow, he will also anxious than you. Brother or big brother, this person usually help to help inconvenient will not help you, not to mention the initiative to help you. Colleagues are willing to help you see mood. So in the enterprise, you have to master a few worship, do not put them as co-workers or boss, so you will grow more assured.
To tell you more than coach for a long time, that to whom you worship?
You are newly recruited junior programmer, you coach the object is mid-level engineers, they teach you things that are more implementation details, this is the stage you need to master and learn; also thanks to senior engineer for the division, but they teach content, most of methodology, this stage is less than that you can use to expand their horizons, to know some of the growth direction. Higher level do not coach, and they speak of content, all sounds reasonable, but you not to fall, listened harmful.
有可能师傅的境界不够，把你凉在一边，怎么办？我讲的所有内容，都是自己主动承担责任，自己主动成长，若要如何，全凭自己。所以我们除了师傅外，也要有一套自己快速入行的办法。
2. 自己承担入行主动权的方法
师傅都会给你讲项目代码，不管他讲的好还是不好，详细还是简单，你都要认真学习。每个师傅讲的过程都不同，我们就不讨论过程了。但是在学习这些项目代码的过程中，有一些目标是一定要达到的。
1）项目的环境要搞懂，自己能把它跑起来；
2）项目采用的框架要知道，代码的结构要搞清楚。
3）项目的各个模块对应的代码要知道在哪里，特别是师傅负责的模块要知道。第2和3点，只要知道大体框架就可以，不需要知道细节。
4）要知道怎么加断点，能根据断点完整调试一个功能。从功能入口到业务逻辑，再到数据存储完整的流程都要知道。这点就要知道细节了，越细越好。
在师傅让你自己看代码之前，这几个目标一定要达到，不懂得就拉着师傅问，这个阶段，千万不要不好意思，也不要怕别人觉得自己什么都不懂。达到这几个目标，你基本上就把代码框架、环境、开发工具相关的问题都处理掉了，接下来看代码，基本上是熟悉业务流程、代码的编写技巧、以及对产品功能的了解。
3. 怎么在看代码中，比别人成长的更快
看代码常犯的错误：
一般让自己看代码的过程，会有几周时间，这个公司不同，时间也不一样。所以我们要用好这个时间。
大部分的新员工，看代码的时候，走马观花，什么代码都看，看了后面忘了前面。几周下来，感觉看了很多，但是问他什么都不知道。实际上，看代码会很无聊，所以大部分新员工，都会在这个阶段，去网站逛论坛，希望看到别人分享的经验，学习开发技巧，然后感觉进步好多。你现在连代码的搬运工都还算不上，去学习如何行云流水的写代码，实际效果是很少的。
正确的看代码姿势：
Better to see more refined look, in front of the first three goals, to let you know that the master module is responsible for, and here comes in handy. You will see the master in charge of the module, able to understand the best, do not understand and asked him, so his knowledge unknowingly to your body, and it is still very happy master this apprentice good for me so worship , look at my code.
Above this is a joke, to see the real benefits of the master code: you look at the code, the master could not read, so he is not guided by his own code, he basically cooked, he does not need to spend too much time can help to you, engineers are busy, he could not spend much time in your body.
4. The ability to develop fast-growing dishonest
If the first three points, you feel confident, and take the initiative to find the master to change the bug, if your bug to master change, then do not read this part later. If you are not sure, or master let you look at the code, and you have the master code is read, or if you've tired of the code. A lot of people will be very lost in this part of the code could not stand, and have nothing to do, the master also let you look at the code, and then generate negative emotions, then the network dream life, so that the occupation is not good.
We have as occupational requirements of people, you need to take responsibility for their own professional growth.
Here to share a method, project data and code are on the svn or git, you can see the code written by the master every day, has been recorded on the code management tool, then the master himself to write code every day, and he wrote it again no matter know anything, right, so you know how to do the function, the master is how to think, how to understand the function, you imitate several functions, on the whole know.
Not so for three months, there is a master seventy-eight successful force.
5. Summary
Master, self-cultivation in the individual. This lesson to share with you, how to learn from the master, quickly adapt to their posts, the initiative to grow on the job, to enhance their coding ability.