Personal Growth Stage

If the starting point is to enter into an industry of small white, then to become an expert in this industry, at least through three stages:

-Knowledge of the original acquisition stage: Just entered an industry, we are "apprentices", do not understand a lot of things, as long as a little action, the brain can feel good growth. After graduation work began to integrate into a team, began to participate in the development of the project, there are teachers, have colleagues to learn, many times you do not want to learn things are difficult. Therefore, at this stage, is the self-technology bursting period, is a rapid growth stage.

-Knowledge of the net accumulation stage: eight years of anti-Japanese war, after the first stage, we all have their own housekeeping skills, technology enough to deal with daily work and research. Busy every day, but the feeling is repetitive work, "harvest is very small." Even if you continue to learn, you will find that many of the new knowledge you study and come into contact with every day is repetitive. The desire to accompany the confusion may be the characteristics of this stage, from the "soul in depth" vaguely feel that they should learn more things, but each time to put into action feel a little harvest, so began to doubt and confusion. In fact, we neglect the most essential features of this stage: as the breadth of knowledge accelerates, the depth of knowledge "slows down", but the breadth of knowledge often gives a "superficial", "useless" illusion. "Guang" In some extent is "deep", seemingly unrelated experience, seemingly irrelevant knowledge points, in fact, after a long period of acquisition, thinking, absorption, suddenly one day, point into a line into the net, people have a "taichetaiwu" feeling, quickly into the third stage.

-Knowledge of the precipitate upgrade phase: Taichetaiwu After the sublimation, the beginning of a new stage of rapid growth.

The curve has only the lowest point, there is no top, so-called "How big the heart, how big the World". As a technician, always be aware of your current position. In addition, I think this curve in addition to the technical staff, should also apply to other industries, mutual encouragement.

I will be at every stage, according to my personal experience, to talk about my thoughts.

Phase one: The primitive acquisition of knowledge

This stage, is to let oneself have skills, can settle down. Simply put, "I have someone else's recognition, irreplaceable value"!

As a technician, of course, the first manifestation in these aspects:

-be familiar with at least one programming language. no matter what the language is, JUST do it, make it familiar, at least to write code handy, basic grammar, advanced skills to understand the chest! A lot of people always like to (correction) than (knot), a language good or B language good, it is like, you see someone drive Mercedes, someone drive a BMW, so you start to struggle after I am in the direction of the Mercedes-Benz, or to the direction of the BMW efforts? Buy Mercedes or buy BMW, tangled this, it is better to tangle: Today I am driving a Mercedes, or driving a BMW!

-be familiar with at least one database . Whether it's MySQL, SQLite or PostgreSQL, or any other rdb. Familiarity is not just about writing "SQL statements that no one else can read", but more about how well you understand and harness the database, such as performance tuning, index optimization, library table design, database design principles, and best practices.

- familiar with the use of various project collaboration tools . This is the basis for teamwork, such as communicating IM tools, code management tools, task tracking tools, Wiki/markdown document editing tools, and more.

The important thing is, whether it is the front end, the service side or the client, let yourself become an expert in one field!

If you do this, you can only demonstrate that you are qualified for a good software development engineer. I feel that it is not enough, at best, that this phase is half done. The other half is more important than your own practice:

-the lateral development of their own knowledge structure. If you are only familiar with a language, or if you use "familiar with a language" to see "another language only know", preach that "PHP is the best language in the world", can only say you are ignorant of the frog. We need to have a comparative perspective to understand multiple languages, to know the pros and cons of each language and the applicable scenarios, to be able to according to product characteristics, delivery cycle, team characteristics, performance and other aspects of the language and frame selection. At the same time, outside the relational database, start contacting and understanding popular Redis, MongoDB and other NoSQL databases to understand the pros and cons of different databases and usage scenarios. Plus, read the good code! read the Good code! Read the Good code! At least you have to read two of the more popular MVC framework source ? "Curiosity" drive, my team and I often say the word is that the code in all you think the more "magical" place, it is worth you to read through the source of magical magic to dig out. For example, how does a requested URL map to your action? How is the context mapped to your action created? Are there tools that you can use without being initialized, without reference? When you can't fill this void with "brain tonic", you need to dig in, until the next time you see a similar magical brain tonic you can figure it out.

-Comprehensive development of individual abilities. Start to carry the project team in the big flag, to solve some other people tricky and can not solve the problem, "solve the problem" to open the distance, this is the addition of the problem! (To make a project, in fact, is a very simple thing, continuous maintenance and operations, is a very difficult thing, personal ability of deep digging, also reflected here). In addition, all-round development is also reflected in the continuous improvement of their communication skills (the closed-loop principle of communication), you can see my other article "and development leader Chat communication", you can take the team, the role of the project leader in the development of the project plan, the implementation of the project plan and completion of the project or product delivery.

This stage, 1 years or 5 years or longer, in my opinion, the determinants are not IQ, but how much time and sweat you pay to get such a skills. If it is your lifelong career, then, to squeeze the potential beyond your IQ, everyone needs to pay the same effort, the only thing you need to decide is to graduate, energetic in the first few years to dig out their potential, or to lengthen the front of a decade eight years? The longer the battle line pulls, the lower the input-output ratio must be, the harder the degree must become. If you don't reach the first point before you start a family, the only pain you'll ever get from work, the advent of any new technology, is just pain.

This theory or idea, I just graduated from the time I did not know, and no one told me to work hard more. Just I think I am lower than others, at the same time is also relatively lucky, in my most energy and time period, in the work, technology development has paid almost all efforts to shorten the gap:

- read a variety of books: no matter what language is used in the project, almost read the classic bibliography of the relevant language

- look at the various code: the project related irrelevant code, read through, the use of open source code, the first thing is to read the source and then hands-on use

- Write a variety of code: try to improve the read-through code, the work also practiced hand a lot of code

Stage two: The accumulation of knowledge in the netting

This stage, more like a person to middle age, can not rely on physical strength, spell "programming code Amount", spell time to improve themselves, but the long road, the development of internal strength Dafa. In my opinion, there are mainly two aspects of cultivation:

-Seize the opportunity to broaden your perspective (broaden your knowledge). Opportunities may be the projects you participate in or dominate over the next few years, as well as your accumulated project experience, and your own efforts outside of your work. Participating in different projects, reaching out to different clients, influencing and changing a person, "experience" is just one small aspect, and the bigger impact is the point of view. Different projects to understand the different industries, the work, projects, products to achieve their own ability to the highest point, become an expert in an industry (to reach the height of their own), contact different customers, and different styles of customer cooperation, communication, so calmly face the kind, hypocritical, unreasonable and other colorful customers, Learn to stand on the customer's point of view, speak the language that the customer understands, manage the customer's expectations up and down, and begin to realize the importance of the team (do you really understand the team?). ), the ability to structure team structures, the growth of members, to bring out products or projects at the same time, can bring out a team to daying Zhang. The breadth of knowledge extends, is a slow process, the work does not know the technology can not, but only know the technology also absolutely can not, and technology outside the field, for technical personnel, learn fine, is also the most difficult place.

-Personal continuous learning (continuous deep digging). Rome, Cold day. This stage, for most people, is the most difficult stage, difficult in a lot of people will give up (anyway I can cope with daily work, meet to bring the stop), very easy to be confused and impetuous (I also want to learn, but every day to see, it is their own will, those who do not know that my work is useless). and correct change of their own cognition (seize the opportunity, correct treatment of their own efforts), is to break through this stage of the premise. The accumulation of knowledge, at the beginning, is like a node in the repository of knowledge of this mesh structure. Each piece of knowledge can be a node on this web, and many nodes at the beginning, you do not know whether it is useful or useless, but also do not know the links between nodes. Just like if you have only two points in your mind, no close is not closed, you can not even, but when we put this structure infinitely magnified, the node more to a certain extent, a lot of knowledge connected with each other, is a very natural thing.

-Social and Friends (war) friends. Find your comrade-in-arms, when you are alone, when you are lost, there are people who accompany you to drink and blow water. Also so-called three people will have my teacher, very grateful for so many years, my side of these friends, also the teacher also friends, let me learn far greater than my own ability to get outside.

So, my personal experience:

-If you have a very clear direction, then down-to-earth, perseverance. There is progress, that is normal, if you do not feel the progress, it is normal. Never put yourself in a result-oriented mindset.

-If you do not have clear goals and direction, but you have to realize that at least you have housekeeping skills, you have to do is to do the things you need to do well, the goal is only you do not know, in fact, "God knows" ^_^.

We is always putting ourself to the perceived world and break it!

Sometimes I also call this method "self-paralysis". When you find yourself in a difficult breakthrough, you either find someone to "paralyze" yourself, or you find a reasonable idea to "paralyze" yourself. Many times, no one told me exactly how to do, I need to give myself a little faith, and constantly with that still a little passion, but also a little dream of me to defeat the satisfaction, lazy, impetuous me.

Think about it, do you have two of me? When you use one I beat another me, either you enter the third stage, or you fall back to the first stage.

Phase III: Knowledge precipitation and escalation

Victory is sublimation.

This stage is the beginning of metamorphosis into the "Great God", which is the process of creating knowledge from knowledge to qualitative change:

-Constructs the model and uses "known" acceleration to grasp the "unknown". We often talk about who is more able to learn than strong. What does "learning ability" mean? Is who can quickly use their old knowledge to master new knowledge, unknown knowledge! How do you do that? Thinking (the abstraction of repetitive business and the prospect of future business development, emphasizing past experience and the foresight of the industry)-"to find the rule rules, that is, the model-" Application Model Rules-"improve." Disorganized things, do not conform to human cognition, only from the chaotic things to find the law, can be accepted by the human cognitive system. The process of finding a law is the process of modeling. A few examples. Technical staff often say (squirt) "This grammar is copied from which language." What do you mean? Because you have a grammatical model in your cognitive system, you are using your existing grammatical model to understand the grammatical model of the new language. What are we going to learn from a new programming language? "Gee, I wrote the control statement in the familiar language," said the new language, "Oh, how I define classes and functions in the familiar language, the new language is so defined." When you see more language, you will have your own cognitive model of the language, and then you will curse: "These creative language of the Daniel should die, there is a problem, with the function of good, you have to change to Func, or to def; I use curly braces well, you have to change to a colon; when I declare a variable, Put the variable type in front, you have to change it to write to the back. ”... If you think so, instead of "PHP is the best language in the world," Congratulations, you've started to have your own cognitive model, and then you're going to abstract out a model: programming languages are actually defined as the rules of the founder of programming languages (good) to make you write, so learn new languages, is to understand the definition of other people's rules, there is no good or bad right or wrong, we are cattle people "heel" just. After you write more code, you will recognize the new language: Get to know the grammar rules, look at the framework, get familiar with the ecology (Libs is not enough, what the application scenario has, and the tools you are familiar with have no similar alternatives in this ecology). All this together is the basis for your technology selection. Another example, the development framework, gives you a new development framework, what do you need to know? The "What to Know" definition is that you know the model of the programming framework: What the routing mechanism is like, what the template mechanism is, what the plug-in extensibility is, what the toolset is, and what the performance considerations and development efficiency considerations are. You can follow the same approach and approach to understanding the TCP/IP protocol: The interpretation of 0 and 1 under specific scenarios (context). With this cognitive model, you learn TCP/IP is actually learning: how many kinds of context, in each context under each bit 0 and 1 represents what meaning. This is also the key to performance optimization. Again, for example, follow thisWhat is the protocol for working with customers outside of programming? is based on the win-win of trust and relationship model.

-Micro-innovation, the summary of known, polishing and upgrading. When you begin to look for patterns and build models, the next thing to do is to use this pattern and model to constantly get to know new knowledge and then return to improve or refine your cognitive model after you get to know new knowledge.

-Finally, you'll have a way of understanding the world from your own perspective. Others tell you that the world is false, you learn from the book of knowledge is also false, only you have mastered their own cognitive methods, in their own way to understand the world, knowledge is for you to use. I have been using a simple "protocol model" to understand and recognize work, society, and the world. Don't laugh. I am young, dare to talk about the world, maybe wake up tomorrow, I will despise my small view, but, at this moment, I have my own understanding of the world model. Two years ago I gave the team a "everything is agreed" training, at that time, more attention to the technology of the agreement, now after two years of improvement, perhaps next time I can share the new "Everything is Agreement" theory ^_^

Finally experienced three stages, think oneself become God, in fact, young man, you are still too young, wake up:

?

Never-ending, by the eye can't forget the height, rely on only your imagination!

Personal Growth Stage