Abstract
Recently, I talked with my friends and colleagues about how to grow as a technical person. Why to talk about this topic, because the career development of programmers is really fast, 2 or 3 years, people with the same starting point may be opened a big gap, so technical people must continue to learn, to ensure a certain growth rate, in order to keep up with the update of technology and constantly beat the waves.
Growth system
Likes and Excels
The career growth system always mentions two dimensions, like and good at. Doing what you’re good at will ensure your career bottom line, and doing what you love will help you reach your life limit.
Most people are mediocre, so do not always struggle to do what you like or good at, because in fact, most people neither love, nor good at, a lifetime of work for decades, you can continue to do a good job in the occupation, do good at, you will gradually like him.
Being a programmer is not a bad job, with decent pay, simple relationships and a high ceiling. Although the number of employees is gradually becoming saturated, which leads to intensified competition, life is not only about work. People in society are always influenced by various ideas. Therefore, as long as you can keep learning and make continuous progress, you will be able to beat ordinary people and stand out in the competition.
Stage of growth
Programmer development path: 1 year for entry, 3 years for senior engineer, 5 years for senior engineer, 7 years for architecture, 10 years for delivery
It describes a rapidly growing profession. Of course, the 10-year takeaway is a joke. The meaning behind it is that there are fewer technical positions in 10 years, so the technical people continue to go beyond the scope of technology, some do management, some switch to products, pre-sales, consulting. Or no longer in the Internet industry, this is very normal, the world is rich and colorful.
Early in our careers, what we can do is follow, keep up. In the middle of my career, I began to have the ability of planning and construction, with a strong heart, and could confidently walk out of a different road without caring about other people’s opinions.
Work and Life
It was about five years into my career that I realized that work and life were inseparable. Work is life, and life is work. Until then, I had always wanted to build a wall that could separate work from life. And what I found out is that in this age of rolling up your sleeves, work is eating into your life, taking up most of your time, and if you’re thinking,
- When I get a job that leaves early, I’ll have time to study and improve my skills
- When I get an easy job, I’ll have time for love
- When I am not busy, I will go out to travel and explore the world
You’ll find that a year later, you still haven’t achieved it. Because you no longer have the ability to live, the job has taught you to be a person who can only passively accept tasks, rather than actively plan your own life.
So think about how you can live as hard as you work, and work as happy as you live.
How to learn
We have our own goals for growth, so how do we learn
Learn as a team and teach others
The three steps of learning are repetition – summary – induction. Find won’t through answer dish, sum up the knowledge point among them, next inductive rise, repeat ceaselessly strengthen. Learning alone is always unsustainable. You can progress faster by forming teams with colleagues and punching in online communities.
Teaching others is the real grasp of a knowledge point, technical knowledge points are objective, there is no only can be understood, can not be said. When you understand a knowledge point, you may only understand 2 points, use 4 points in practice, summary 6 points, can teach others, you understand 8 points.
Knowledge map
Technologists must build their own knowledge graph, connecting dots into lines and lines into surfaces. For example, this is my big knowledge graph on the back end of the Web, each of which has this knowledge graph in it
Because then your body of knowledge is structured, and structured knowledge can be searched quickly, just like text search, you can’t search quickly without building structured data.
So how to construct their own knowledge graph? Start small, starting with daily accumulation.
Every bug that takes you a long time to solve is a sign that something is missing. You can fix this bug by asking someone or StackOverflow, but take the time to figure out why it happened, how it happened, and build it into your knowledge graph
Start by extending you assign a requirement, do a task scheduling. You can use the task framework packaged by the company to quickly implement requirements and deliver them. But this is not the end, you need to consider
- What problems need to be solved by a task scheduling
- Solutions in different service scenarios
- How does the mission framework address these issues
- What other frameworks/technical solutions the industry has for task scheduling
Learn to expand your learning to broaden your horizons.
Learn the industry’s body of knowledge and develop your Map. All of this is learning on the job, but there are only so many scenarios. So learn from others, learn from the industry. Such as how distribution works and what problems need to be solved to help you refine your atlas.
Follow the public account [Abbot’s Temple], receive the update of the article in the first time, and start the road of technical practice with Abbot
