Many people have asked how technical staff to grow, and how each stage, how to get out of the current confusion, achieve breakthroughs in your life. So I combined with my own 10 years of experience, summed up the technical staff to grow 9 Dan, I want a career, help.
1.
New to programming, will think this is a very magical thing, plain letters, plus punctuation, could have so much magic. Programming will feel is very proud thing, because in our view, it is the creation, by beating these characters, create the effect we want.
I was the first time that programming, is this feeling, I do not know what it is, how to do it, but feel it is very magical, do not know but feel a cool feeling, then will be fascinated, I began to want to learn.
2.
I started to learn programming choice is no choice, because do not understand anything, may be the first where to see, learn what to imitate, and then embarked on a program of road.
I was first exposed to language Pascal language, I did not know what it is, just know it by that name. This language was in high school, on the computer books, I learned some, not so much to learn, remember not the case, because I have not practiced, is not running before.
3.
After embarked on the road of programming, learning grammar was mainly to see the way, this is to get started, but did not quite know why, but can, to imitate, this time be regarded as a beginning.
After the introduction, can not wait, using a variety of experimental results, and these results may not write itself, as a beginning, the environment can build, run, it will copy some code from many places, try to run, then feel pride after the success.
I really do something out of language is VB, you can drag generated by the interface, and then fill logic code you want, you can achieve some functionality, such as MP3 extension processing, HTML turn TXT, then the main purpose, or to meet their own needs, you can do some cool stuff, not really regard it as learning a skill system work for it, but even so, it has been enough for me to be proud of in front of their classmates.
4.
Prior to the real work, this time to learn, it began systematically, after all, decided to rely on this to make a living. This time we'll look at some real class books, such as how to do website, by what framework, what database server to use, and so on, this time to basically the right way.
But this time, we'll just use the stage, most people do not know why, such as the Spring framework, so we know the configuration can be reversed IoC, but do not know how to achieve, what principle yes.
This time the biggest feature is that the work can be assigned to do, less likely, it can be resolved through Google, Baidu, big deal to copy someone else's, you can change to change.
Anyway, now we have begun to have a system architecture framework, you can make a living.
5.
With the increase of experience of working longer, you will gradually develop, many common knowledge that he would only use, but do not understand, such as allocating memory, loading order of the class, IoC principles and so on.
This time is probably about 2 years of work, if fast, it may be realized in the first year of work. This time you will deliberately buy some books to explain the basis of class, such as had never seriously read the "Thinking In Java" began to re-read, and read very carefully, but also with the test example, if like a just getting started, but you know you are very clear about what you are missing that want to learn anything.
Then you might also try to buy some more in-depth books, such as to explain the principles of the advanced features analysis'll have to wait, this time you will gradually start deep in the language you are now, not only will be used to cross, but also understand why phase, which is lonely, because most of them are language features, principles of learning.
Cross over that fish big splash, go through, it is a repeat of the screw.
6.
Congratulations, you can come to this stage, you will not only use, but also to understand the principle. This time you may have more than three years, and this time you begin to independently responsible for a number of projects, you are designed to do. This time is not only a test of your programming language itself, you will also consider how to make your projects with better scalability, how to improve performance, and how the database server, with caching, design a better system.
At this time you may begin to see the design patterns will optimize research database, you may also study for Nginx, in order to better use.
The main feature of this time, that is, the ability to abstract, design your own project multiplexing capability, component-based, modular upgrade, and can better coordinate and match the periphery and programming (database, servers, etc.) to complete.
This is the way to become a senior engineer of.
7.
Now you have come to paragraph 7, this section is a senior engineer, is to strengthen paragraph 6, does not have a qualitative breakthrough.
At this stage, you will have an abstract, architecture deeper understanding. Began to accumulate more modules to form a micro SDK or a service, you start in-depth study of security, concurrent monitoring. If you are a server, you might consider the service active-active or even live, consider the gateway, and so on.
And you may have to start understanding across multiple end collaborative business architecture and design, such as separate server and front-end, and the end of the service, start problem, designing the system from the global progressive thinking (not limited to its own technology stack).
At this stage, it is to continue in-depth paragraph 6, accumulation, extension, and then accumulated to break through to the architect.
8.
Now you finally break through to the architect, your vision is not limited to your technology stack, other languages you may not know, but you know how to use them, even you start learning another language.
You design the system, will not only consider their own technology stack, you might choose a more suitable technology stack to achieve.
You will cross-language, thinking technology stack, and can make a good project plan, such as responsibility, across the server, Android, iOS and the front end, you will take into consideration, taking into account the technology stack brother, coordinate this project.
You may only complete the assigned tasks, but also put forward the existing system more constructive proposals to optimize, improve, or even the accumulation of our business needs technology platform, advance knowledge, to do for our future use and expansion ready.
You will be familiar with the business, the business may be more familiar to more people than any other, because the only way to design a more suitable business architecture.
You will help the person in charge of technical ability, to help you promote coordination of things that make you a better idea of the development and realization.
Consider your point of view, always the entire technology sector, not again confined to a project, a group, a technology stack.
Then congratulations, you are now a qualified architect of.
9.
Now, to paragraph 9, and now you may have done for 10 years, you find that all that technology, tools business are realized. Business is fundamental, technical services for the business, if the system will be able to buy a purpose, it does not require their own development.
At this time, you have the ability to scale again, you can transverse to the product, marketing, operations, design, testing, operation and maintenance and so on, this time, you are not just a technical person.
If there is a call, it can be technical director, technical VP and so on.
10.
Paragraph 9 above, combined with my own 10 years of experience, summed up the growth of the technical staff Dan 9, paragraph 5 is more important, is a threshold, paragraphs 6, 7 is an accumulation phase, but also cultivate abstract stage architecture capabilities, these two stages, you can decide whether to architect paragraph 8, paragraph 8, it is also a threshold.
Some people may be more than five years will be to paragraph 8, it may take 10 years to get to in paragraph 9, which is a very difficult process that requires long-term accumulation of metamorphosis, thought to grow to in paragraph 9.
From the beginning of paragraph 6, you can not be selfish, and to consider more coordination, collaboration, systems, multi-angle. Only thing to do is to get the whole team to benefit, in order to gradually break in paragraph 7, paragraph 8 into the architect.
Every step, step on solid, more thinking, more learning, in each Dan, Dan can do some things beyond this, it is natural to enter the next Dan.
