How do junior engineers grow quickly and seek breakthroughs

This is the 81st unwatered original, want to get more original good articles, please search the public number to pay attention to us ~ this article first in the political cloud front blog: how to grow quickly and seek breakthrough junior engineers

preface

The purpose of writing this article, because see a lot of newly hired students confused, no sense of purpose, saw some classmates 1-2 years work on business development without a lot of growth, 2 ~ 3 years has seen some of my classmates work time into a framework of “working people” skilled, but no good sedimentation and window, result in unable to enter the company, So I wrote this article in the hope of giving some inspiration to these junior and mid-level engineers.

Choose the right platform

Choice over Effort

If you get the Offer from the following two companies, how will you choose?

	A company	Company B
The size of the	400 people	1000 people
industry	The Internet	Software services
salary	10 K	13 K
The number of the front	Forty people	80 + people
Functions of the front-end	Independent front end	To follow the project
Report to the boss	Professional front end	The back-end

I believe that most people will choose Company A, because you will agree that Company A has more room for growth and will accumulate more precipitation, so why do we make such A choice?

Which aspects to choose

1. Looking at the industry, e-commerce before 2010, education in the past two years, community group buying, etc.

2. Look at the company, whether it is a big factory, what is the influence in the industry, and whether the company culture matches. You work with the right people, and the results won’t be too bad.

3. Whether the position is a functional department or not mainly depends on whether there is an independent front-end department in the organizational structure. Many companies have a lot of front-end development, but it is scattered in different departments, and the report boss is back-end development.

Where do you get the real information

1. Ask for advice. Now that the Internet is so developed, if you visit the community, it is easy to get the contact information of the industry leaders, let them give you some advice, basically can give you a judgment, such as Scott, who is more active in the community.

2. Internet search is a bad idea. Online questions, Baidu search, pulse and other information is complex and not necessarily objective and fair, and the answer to your people may not be the same job with you.

Don’t worry about the two grand

When you have multiple options, many people say the one with the most money is right. But at the beginning of your career, it’s important to focus on growth, not on a platform that’s not right for you just for the extra two thousand dollars. Most people’s salary increase is the most 3~5 years of that period of time, in front of a good foundation, there is enough accumulation, the back is when you pick a platform. The rewards are far greater than the amount of money you spent before, and can even affect your career choices.

Integrated into the team

When you enter a new team, you must first fit in. If you don’t fit in quickly, you’ll be eliminated or, in the worst cases, you’ll lose at least a year, and each year counts (more on that below). How can you tell if you’re a part of the team? It doesn’t matter if you laugh, drink and play games with them every day. Some people are naturally introverted and don’t talk, so they can’t be part of the team. It’s whether everyone on the team behaves in the same way, whether they have the same cultural values. So how do you fit in quickly?

1. Stay with your team. Newcomers to the workplace tend to share meals with alumni or friends who came in with them, while alienating their own teams. The so-called “get along” way, if not often “around” together, always outside the team, will be more difficult to integrate into the team.

2. Be proactive. A mature team Leader or senior will certainly provide you with some training opportunities. Generally, it will not be a command-style arrangement, but to ask “who is interested in this matter”. At this time, you should dare to take on responsibilities and dare to speak out, and at the same time, you will get the opportunity to be directly instructed. Don’t be afraid to mess things up. Do not necessarily have a return, do not do never harvest.

3. Be a reliable person. Being considered reliable is a high rating, so what does it take to be reliable? My understanding is that everything has feedback, everything has results, everything ends with me. Does not belong to me is responsible for things can tell each other about who is responsible for, not sure on the spot to give clear feedback on time, and timely feedback and synchronous others actively, rather than wait for someone else drives ask you, all the things he is responsible for need to have a clear as a result, the process need timely synchronization, the people who need timely feedback to the corresponding risk, and push things fall to the ground.

The rapid growth

After choosing the right platform and joining the team, we have the soil to grow quickly, so how can we grow quickly? I understand growth to include two aspects, technical ability growth and professional ability growth.

How to improve technical capability quickly

• Insist: many a little makes a mickle, focus on insist, build their own knowledge system. I, for one, now read at least one technical article a day.

• Write more, practice more and think more: collecting, reading and liking does not mean learning. In the first few years, you should write more and practice more, until “the code in your mind is finished when you see the requirements”. Reject meaningless copycat code and think why? Behind the design scheme thinking? There is no better plan.

• Be humble and dare to question: Have a humble attitude and stand on top of others. If you have the “best Lao Tzu attitude”, your team will soon beat you to death. Be good at finding the good in others. Modesty does not mean that we do not speak out. We should dare to challenge others in the discussion stage, dare to express our ideas, dare to question the imperfections of others’ considerations, speak out more before the event, not the person, and do not speak out after the event.

• Do a good job: to develop the habit of excellence, do not feel complacent because each task is completed, completion is a basic requirement, is what you get paid to do, do a good job is a reflection of your growth, when excellence becomes a habit, growth will be fast.

• Dare to practice: some technical articles read is not equal to will, there are good best practices and technical solutions to dare to use in the project, the business verified solution is a good good solution, but also can let you quickly master these related technologies. Of course, it is a good practice to share and discuss within the group before implementing.

• High profile: This is the easiest and the hardest. Too many programmers have a good idea dare not say, or only to a few people say, make a good tool good plug-in only for their own use or only for a few people around amway. Be willing to express what you see and give advice when appropriate. A good tool needs to be actively promoted to a large team or the entire r&d team. Proper high profile can let more people see you, there are relevant opportunities behind others will be the first time to find you. For a tool, the more people you use it, the more problems it exposes, and the better your ability to solve complex problems. When proactive excellence becomes your label, it will bring you more sense of accomplishment, self-confidence, motivation, challenges and opportunities.

How to improve professional ability quickly

What is professional competence? Professional ability is the comprehensive ability of people to engage in their career. For R & D, it usually refers to the comprehensive ability in addition to technical ability. In my opinion, the most important professional abilities in the workplace include communication skills, business skills, collaboration skills, feedback skills, planning skills and summary skills.

There is no standard answer to how to improve these abilities. Different talents and personalities have different ways to improve. I have summarized some personal experiences here for your reference.

Ability to communicate

• Language consistency: in the face of different types of work, such as testing, back-end, product and business, first of all, the language should be consistent, your language expression should make the other side can understand, if you always say professional vocabulary, others will not understand, to professional vocabulary into others can understand the language. You told your boss that Vue/React’s data-driven model is probably not understandable to them. However, if you told your boss that Vue/React is the mainstream development model in the industry, which can improve the efficiency by XX% compared with traditional development and save much manpower, the effect will be different.

• Understanding consistency: if you are saying A and the other party hears B, you think the other party is also saying A, then there will always be only “ditch” and not “through”, even in disharmony. I have met many times that they could not reach an agreement for half a day and finally came to me for coordination, only to find that the two people were not on the same channel, resulting in ineffective communication. In this situation, I usually listen to the story first, then give my understanding, and then repeat it to the other person, asking if my understanding is correct, rather than rushing to express my opinion.

• Use more hands and speak less: language can be easily misunderstood in the process of communication. For example, when I describe a person’s face, 1,000 people will draw 1,000 faces. If I take out a photo, I can accurately transmit information. In the process of communication, more drawing, more demonstration, use whiteboard, can improve the efficiency of communication. In the process of saying, say the key points, say the conclusion first, then explain. Because maybe some people don’t care the explanation, just need you to give the conclusion. When there are too many explanations that don’t lead to a conclusion, they may be perceived as being verbose and missing the point.

Business ability

• Be a “fool” to yourself: a good product should be cheaper to learn. Make a fool of yourself and use the business product you’re responsible for, and you’ll find too many points to optimize.

• More perspectivethinking: don’t look at the business from the perspective of technology, but think about who the users of the product are. The core is to solve the user’s problem, whether it has been solved, and how the feedback is.

• From a company perspective: What are the upstream and downstream dependencies of your business? What role does he play in the department? Where does it stand at the company level? Looking at the business from different perspectives will give you a different perspective.

• Pay attention to competitive products in the industry: what is the trend of the industry, where are the advantages of competitive products, where are our advantages, and maintain a certain sensitivity to the industry.

Cooperation ability

• Find common goals: Through good communication skills, find common goals. Magnifying shared values makes it easier to work together.

• More empathy: more standing in other people’s point of view to consider the problem, ask each other what your difficulties are, how I need to help, understand the appeal, and then put forward a targeted solution. Instead of coming up with “what am I going to do”, say more “what can I bring to you”.

Feedback ability

• Awareness: Having feedback on everything is very, very, very important awareness. Imagine these scenarios: 1. If the person in charge of a development task asks you once a day where you are and whether it has been completed, you don’t ask, you don’t tell; 2. Some people in the group feedback you responsible for the page out of the problem, and you have not read back — in fact, you may have been in the investigation, or have more things to deal with, but you did not return, others will think you are irresponsible, and even think that the whole team does not have the Owner consciousness.

  These two states are very bad, if we can take the initiative to report the progress of things, if busy when we can return a “watching”, “in the meeting, after 5 minutes to see”, the effect will be different.

Planning ability

• Set goals: without goals, there is no motivation to persist. Before doing, we should set goals first. Goals can include long-term goals, medium-term goals and short-term goals, which can be set according to their own planning.

• Set a period: All goals should have a clear time node, without a time node, it is difficult to progress.

• Do the disassembly: The finer the granularity of the disassembly, the better the performance, we can continue to disassemble until we can’t.

Conclusion ability

• Practice: Many developers can do but not say, say and not write. My experience is to practice more, practice more will feel. When I was a student, I could write less than 600 words. Now I can’t stop writing thousands of words at a stretch. Usually write more business documents, technical article summary, also can exercise your summary ability.

• Force yourself: Summary is not a running account, to simplify the complex, many people will say that can not be streamlined. My experience is to force yourself to do it, for example, 5 minutes to summarize the highlights of the first half of the work, only choose one thing you think is the most need to say to the boss, the sum of no more than 100 words, and then it will be clear how to do the summary.

How to find a breakthrough

As technical capabilities continue to grow and professional capabilities grow, how do we move to the next level?

Technology feeds business

• Find solutions from the scene: Technical ability must be able to feed business, in order to reflect the value of technology, learn new technology and new knowledge, if not applied to the project, then always just a Demo sample. So instead of looking for scenarios for technology, look for solutions (technical solutions) from scenarios.

• Smart lazy: Try asking yourself: How can I work less and still fit the business scenario? This requires you to understand the business and come up with a better technical solution. The rational application of technology in business can not only improve their technical design ability, but also better support business development. Of course, “less work” here does not necessarily mean less work this time, but in the long run to think about how to expand and save manpower.

Look for opportunities and land quickly

Some people have been complaining that their talent is not met, there is no space and no opportunity to do things, good opportunities are occupied by others can not get a hand in. In fact, it is not the lack of opportunities, but you lack the eyes to find opportunities.

• Find uncomfortable point: uncomfortable people are opportunities, pay more attention to others’ complaints, pay more attention to what you think is bad, ask partners where they are uncomfortable, as long as the uncomfortable point is an opportunity. For example, whether the team scaffolding tool is good, whether there is a monitoring system, whether there is something that needs to be upgraded or checked by all the people, whether the test needs automated tools, whether the product needs a business reporting system, whether the operation and maintenance need to deploy the management system. Pay attention to the dissatisfaction around you, don’t always avoid the dissatisfaction, but pay attention to whether there is an opportunity to come.

How to judge your growth

How can you tell if you’ve grown? How many components were developed, how many pages were implemented, how many versions were released, how many days of overtime?

My logic is look what you’ve changed. For example — because your assistance runs better, because you have 50% fewer online breakdowns, because you are 30% more productive, because you have a better team atmosphere, because the people around you have grown. What changes you bring to the table naturally leads to growth in some areas.

Common misconceptions about

• A year jump: a lot of people frequent job-hopping, to where feel oneself “lack of talent”, and often job-hopping can bring about new unit of choose and employ persons to also feel your stability is poor, be here in me also stay a year at most? It is also unlikely that a jump a year will precipitate accumulation. So be careful to choose your platform, know what you want, don’t be impulsive for a little more than two or three thousand dollars.

• Take business results as your own: This is the most common misconception. Business KPI is achieved every year, every year is the star business, but it is mistaken for their own results, resulting in the illusion of annual growth. Try asking yourself: What is your role in this? If you just implement the interaction, can you consider that you have been doing the implementation mechanically for two years? Again, ask yourself what has changed.

• Platform dependent: Some people can’t do things without the platform and have to be platform independent. At different stages, you can choose large factories or small and medium-sized factories, you can choose vertical development, you can also choose horizontal trading space.

conclusion

Growth, like mountain climbing, at first everybody in the same starting line, talking and laughing together, someone stick to reach the top of the hill, in the process of someone parked in the mountainside look at it for more than one yourself, some people choose the wrong road, never reach the top of the mountain, someone choose the suitable way, soon arrived at the top of the mountain… There will be many ups and downs in the process of growing up, but the sense of accomplishment you get from each breakthrough will keep you going. With a little luck of persistence and choice, the rewards will fall into place.

Come on, workers!

Recommended reading

Teach you to build enterprise-class NPM private warehouse in minutes

Writing maintainable quality code: Component abstraction and granularity

, recruiting

ZooTeam (ZooTeam), a young and creative team, belongs to the product RESEARCH and development department of ZooTeam, based in picturesque Hangzhou. The team now has more than 40 front end partners, the average age of 27 years old, nearly 30% are full stack engineers, no problem youth storm team. The membership consists of “old” soldiers from Alibaba and netease, as well as fresh graduates from Zhejiang University, University of Science and Technology of China, Hangzhou Electric And other universities. In addition to the daily business connection, the team also carried out technical exploration and actual practice in the direction of material system, engineering platform, building platform, performance experience, cloud application, data analysis and visualization, promoted and implemented a series of internal technical products, and continued to explore the new boundary of the front-end technology system.

If you want to change the things you’ve been doing, you want to start doing things. If you want to change, you’ve been told you need to think more, but you can’t change; If you want to change, you have the power to achieve that result, but you are not needed; If you want to change what you want to accomplish, you need a team to support you, but there is no place for you to bring people; If you want a change of pace, it’s “3 years of experience in 5 years”; If you want to change the original savvy is good, but there is always a layer of fuzzy window paper… If you believe in the power of belief, that ordinary people can achieve extraordinary things, that you can meet a better version of yourself. If you want to get involved in the growth of a front end team with a deep understanding of the business, a sound technology system, technology that creates value, and spillover impact as the business takes off, I think we should talk about it. Any time, waiting for you to write something, to [email protected]