Everyone wants to be a big cow, but from the number of people intercepted it?

Become Daniel: I hope that boast Jiao very, very strict practice regardless of the development, inspection, operation and maintenance, each more or less have a technician at heart a technology Daniel dreams.

　　What "always have hope, if completed it"?

　　But many newcomers Ali, after the job will find that hope is to become a big cow, but to do the job with the big cattle seem not detached.
　　For example, the programmer says "every day to write business code also overtime, how we transfer technology to become big bull", said inspection "check every day to implement endless use cases", said operation and maintenance "carry the machine unplugged network cable, knock shell command, this is not I want the operation and maintenance of life. "
　　I am also a programmer, so I want to go through the following example, program development, according to some, with my history give us some see.

　　Typical Myth # 1: thanks to Daniel for the division was thought to become technology cattle most simple direct, fast useful approach is to "worship team technical Daniel as a teacher," so that they always give you special treatment, give you allocate some difficult mission. I was hostile such an approach.
　　Daniel was busy, maybe not quite alone give you special treatment, but do not give you maybe open one hour a day of special treatment. And a team inside, Daniel often assumed special treatment, will inevitably lead to questions about other team members, I personally think that assume team Daniel true heart, give the team the best practice, but a practice very time-consuming preparation.
　　Because the first reason, it is generally to find Daniel, all with questions to ask might talk. Because the answer might not need too much time talking about the problem, more it relies on the accumulation of history and, in this case large cattle are very happy. However, special care should be: Assume often ask those books probably google can easily be found in common sense, large cattle will be very patient, what time is precious. Let friends often ask me, "How -Xmn parameters jvm equipped with" this kind of problem, I have a direct answer, "Please go directly to google", because this problem is too much truth, assuming that you do not go learning system, each have to ask yourself and others is very wasteful of time. About the most part, wants to become a technical Daniel, still the most important to understand the "first on our own," the reason, do not want to have like a martial arts master Daniel hands the same step by step teach you. Appropriate division can pass and perhaps ask Daniel Daniel talk to their own travel, but still most of the time is their own systematic, targeted travel.

　　Typical Myth # 2: The same business code very fast hardware business code technology is the foundation of every programmer, but only grasp these skills can not be the technology Daniel.
　　Like the game Daguai the same promotion, began to fight mobs, curriculum vitae value is high, the more value to the history behind the less traveled can not fight mobs now resume worth it. The division needs to play some more advanced blame, brush some copies of the challenge, the game just did not see what has always been able to rise to the top of the fight mobs.
　　Daniel is a technology road is similar, you have to keep traveling to their level, then while the provisional bigger challenge after challenge so that their response to these levels even higher level, and so forth, what technology arrived even Daniel large cattle industry situation.
　　Write business code only this fight Daguai a road cut nothing, and I thought it was relatively early in a fight.
　　So I thought: business not good programmers write code must not become a technology cattle, but only the business written code programmers can not become a technical Daniel.
　　Typical Myth # 3: work too busy, no time to learn a lot of people think that they do not become a technical Daniel is not that they are not smart, nor are they done, but under the country's environmental, technical staff have too much overtime, leading to their rated no time to learn.
　　For this reason there is a certain objectivity, Europe and compare what we do to be more of overtime, ( shenLi2000 ) but this element only needs to defeat a problem, is not insurmountable gap, what is around us still have so much Daniel is in this environment of growing up.

　　Mistakes lead to constitute such a concept
　　1, go to work to do the job is repeated, it is necessary to travel in order to study rated their own

　　primary reason for this misunderstanding is still composed of that thought, "write business code is no technical content", and I go to work now is to write business code, so I can not travel in the job.

　　2, the learning needs of a large segment of successive time

　　many people think should be like campus to learn the same lessons, give you a full day to class considered learning, and we always work overtime and are more tired just want to sleep late on weekends, perhaps only I want to see movies play games to relax, so there is no time to study.
　　Practice on the practice just the opposite: we should first study and travel in the job, because there may be instances Referring to apply their knowledge, learning effect is the best; secondly after learning the job does not require a large period of time, but rather out of time , using fragments of time to learn.
　　The correct approach 1: Do More

　　to do more, do more than your supervisor to arrange your mission more. To have a chance, you have to prime the crowd coming out, to come out, do you have the necessary extraordinary, to be extraordinary, you have to do more!

　　How to do more of it?

　　1, for more business
　　whether it is not that you served; Learn more code, whether it is not what you write, learn more about the many business interests.

　　2, understand the end
　　"systematic," "global," "comprehensive" These words seem relatively empty, but in fact the essential nature of all technical Daniel, to reach such a situation, it is necessary to understand more system, business, code.

　　3, self
　　Generally more seasoned team, perhaps because the structure of the components have been carried out many of the package, write business code to use the technology really is relatively small, but we have to understand "the only constant is change only," perhaps structure to improve, the components may have to replace, maybe you change a company, the new company neither assembly nor the structure, you want to start from scratch to do.
　　These are opportunities, but also to meet the challenge, and the opportunity to fight there will only be assigned to prepare people, so in this case we increasingly demand more self something, because the real use of time-division ratio and no time has now come to learn.
　　The correct approach 2: Do Better
　　to know that there is no perfect thing in this world, you as a systems and business, there is always unreasonable and can improve local, these "unreasonable" and "improvement" of local, are more other high-level monsters, you can add more kick down the hysteresis value.
　　Identify these local, and gives the solution, and then presented to the competent, once not twice, any more several times, only once landed, this is your chance.
　　You just think, in fact, can always be found to improve the local; assuming you do not think the system where improved local, then state your level is still not available, you can learn the relevant technology, multi-industry look at how other excellent company do.


　　The correct approach 3: Do Exercise
　　in the exchange of time-division level homework and found that many students are really check Do more, Do better, but in the implementation process, almost everyone is experiencing the same problem: having to look at the role of poor, how to do?

　　Share my personal history, in fact, three words: Learning, Trying, Teaching ( dongzhengdyes )!

　　1, Learning
　　this is the first stage, read a book, google, watch videos, look at the blog can be, but one thing is to pay attention to "the system" and especially some basic things.

　　2, Trying
　　This process is to answer questions about key points of many students mentioned earlier, it is the image of the "golden clothes Yushi into their own hands", that is to establish some of their own to check imitate the environment, wrote some of the identification process. There are many ways, not list them here, briefly, it is to want to try to learn something real, just tune even more deepen understanding.

　　3, Teaching
　　in general, through the Learning and Trying, can hold about 70%, but to grasp the truth, I feel bound to do can tell that clear. Because talking about midnight, we will not only demand a common sense point of the system, also needs to consider a variety of details, which will facilitate our further consideration and study.
　　Together, look after perhaps hear people speaking out can have a different understanding, perhaps the new compensation, which is equivalent to continue to improve the technical knowledge of the entire system.
　　Summary: enthusiasm and love is the selective effect
　　become the technology although it is hoped Daniel boast Jiao, but have to pay a lot, whether it is still the Do more Do better still Do exercise, all demand time and effort. This process probably bitter force, or maybe very monotonous.
　　These are actually on the way, but the real action from the selection, in fact, still our enthusiasm and love for technology.

　　Hard power

　　're talking hard power, which is technically true accumulation.
　　How to show your technical strength? I always divided into: technical depth and breadth of both technologies. Technical breadth plain speaking, that you understand and apply the basic principles of the technology points. In the first round of the interview the interviewer will usually ask a number of technical points to check if you can use right.
　　Inadequate preparation of the interview, complete waste of time, but not as their own (assuming that title is high, when I did).
　　Under today to share our needs in the changing of the guard preliminary outline of Java interview, during which most of them are face questions in the interview process, you can control this leak filled, of course, must not listed here might conceal all approach.

　　Soft power

　　Soft power in the interview process is particularly important (there really is more important division), the primary means of communication and the interviewer, discourse methods and approaches to express a problem, logical thinking ability.