For the novice zero-based front-end, he knew a front-end entry-planning know the sooner the better.
1. Targeting
One reason for the confusion and anxiety because there is no goal, do not know where to go.
For any technical positions, there are two fixed direction: technical experts (architects) and project managers.
The former emphasis on technology, you need to delve very deeply in the current field; the latter tend to management, you need to have a deep grasp of the technology at the same time, can lead the team to complete the development tasks of the project.
Which is better, here is not an appropriate answer, everyone had different experiences of choice will lead to a big difference, if you are interested in technology, the technical expert is a very good choice, if together with the team for more confidence to do business, the project manager for you. If you two do not how cold, you can try to change the track, such as product manager for this post, but the post is really the product of more recent post from the front end.
Then you have to determine the direction of the efforts in this direction, then how can we reach that point, theory suggests that to become an expert in the field, need to accumulate ten thousand hours. That is ten thousand child's law stated, the theory behind this law is that people can repeat the exercise so that neurons in the brain of some kind of contact.
Here a technical expert and development manager process, slightly different points of interest. Grow as technical experts, to pay more attention to implement the technology itself, including logic, architecture, design patterns, and so on; and grow as technology manager, will have to pay more attention to the development of process technology, consider how to improve development efficiency and reduce development costs, improve the quality of development and so on. Everyone's energy is limited and selective attention in their favor one side can really deep specializes.
2. do business or do architecture
do business, time-tight, high code quality requirements, refer to code more, business knowledge needed to learn. Do architecture, a little free time, to experience high demand, no reference code, need a deep understanding of professional knowledge; most important, do you both infrastructure development, but also a user, or PM, only 80% - 90% of the clear objectives, and continue to fine-tune the final goal in the development process.
For a newcomer, in fact, do not tangle, doing business is a good choice, but to do high-tech, using the popular technique of business is the best. The reason is simple, the ultimate aim is to solve the problem of architecture among business, you did not do business, how can I know the problems of the business where you do not know what problems to solve, how to do architecture.
So, from a business to start, it is the best choice for newcomers, is the only viable option. The selection of technical content, business reasons to use technology more popular that growth, so that you may grow faster growth path may be more direct. Of course, this is only "possible", different people for different business, so do not insist on certain "high-tech, using the popular technique" of business, but more change themselves to adapt to the team, to adapt to the business, so as to more grow quickly.
In fact, many times you will encounter a very very heavy operations without additional time to study the situation. And how to grow faster in this environment it? That the white copy. The study into the work, is the best way. Do new projects, refer to the old project code; make new demands, the old code reference needs; not the same type of code, reference code other business. The experience of their predecessors, on the shoulders of giants, will grow faster.
This time your mentor and the company leads the way in the actual development process of give you a little guidance you can also complete the timely processing business.
In summary, the rapid growth in the heavy business environment, you need a very good learning ability, very durable patience [which is also a good ability of programmers needed] and a good mentor and colleague, so as to grow in technology more effective way.
3. Learning Technology
This is the core of the problem, how to study for a new technology? I give advice: Do not gulping, first the currently used techniques and thoroughly cooked, is the most important; do not yet thoroughly understand the technology before the current use of, to learn something new, regardless of the new as what the fire. Like mentioned above, different frameworks have different core, there are different ideas. Two ideological framework code similarities are not necessarily similar, for example, Angular and Vue have a two-way binding, although a similar effect, but the realization of ideas and internal implementation is different. You will be flooded with the entry phase of the mind is still all kinds of ideas, but will be more clear.
After some time, when you thoroughly understand a system architecture, you can see the analogy to more architectural system. At this time, you will find a lot of different architectures are the same thing, to understand quickly.
Of course, a thoroughly understand the system architecture, it was a year, someone needs three years, others may take longer. Why is there such a big difference? Because some people in development, do not think that can be completed, will be in development, the pursuit of beautiful code, will continue to optimize their code, so that my code performance better, more readable, and by the time accumulation, to the extent that quantitative cause qualitative change. Even a very clever man, not "quantity" can not "qualitative change", and it is just that the law of ten thousand hours, but his amount may be less than other people only.
While studying architecture at the same time, do not ignore different from the most basic things, one is the technical foundation, is developing a specification.
Everything is based on the development of technology, architecture premise, without a good foundation, it is unable to make your own skill level to achieve a sufficiently high dimension. For example, you do not have a thorough understanding of inheritance, it is hard to understand the internal clear React implementation.
For the development of norms, I pay special attention when trainees get them to comply. For zero-based code that not many students in general, have not formed their coding habits. At this time, began to comply with certain norms, it will encourage them to develop a better coding habits, lay the foundation for future growth. Next, list what benefits the development of several specifications, so that we understand the importance of standardized code:
Standardized code can promote teamwork.
Bug specification code can reduce the processing.
Specification code can reduce maintenance costs.
Standardized codes help code review.
Develop a standardized code habits, helps programmers to their own growth.
These details are not trained to emphasize the other, only I really did develop, own and develop a set of norms, can really go teach other students.
4. Other aspects of learning
as a front-end, two aspects of the study is that most products and designs. The two things you learn is equivalent to adding a dimension to compete with others
Learning products thinking that will help you review your products developed from the user's point of view, to find out the user experience is not good, bad place to interact; and learning design, it does not help the cause of your excellent place to analyze and find solutions . Of course, everyone's energy is limited, it is impossible to learn these two aspects particularly deep, but the best should have contact with a certain depth of learning.
Summarize
earlier and not directly with you explain how to do career planning, but from the direction of development, learning technology, the main business scenarios to give you an analysis: the front-end, what needs to be done and which do not do what must be done and what can be done . We can according to the characteristics of their own interests, abilities, and project themselves in and taken in conjunction with the company, decide what to do, what not to force yourself to do what, what have spare time to do so on a similar decision. For example here, for example: My goal is to become a technical expert, so I want to deeply rooted business one to two years, strict control of their own code standards, in-depth understanding React system, the mobile terminal main React Native, and there time to see Node Babel and related tools, the goal is to achieve a thorough understanding React technology and Web Component development ideas. When you have such a goal, you can clearly know the purpose of their own work, you can clearly see their growth.
Note that if you already have a job, your career planning must not be out of your current job. Practice makes perfect, work to bring you practice environment, growth is your source of nutrition.
No matter what evolved into the front end, it is always concerned about the user experience, this is actually only just end nature of the Internet increases, the development of fashion also increased it.
End:
As a rookie entering the front end of a circle, perhaps something you described above do not fully understand, this is no problem. Make a plan for your career, do not hurry, in fact, the best is working for some time to really determine what they are really interested in.
Also I am currently at the front line of small class courses have classes, and now I have personally taught by the teaching, the front and rear ends of the main teaching, help you develop a career change when detours.
