Soon, too soon, find themselves in this industry has fought for eight years, thought I alone have project experience and experience how a person should be regarded as a comparison of the qualifications of the industry, but this year the change the work process has suffered a major setback. I will not describe in detail the process, in this, I just want to talk to you a summary of it, see if they have no similar experience, and a similar sentiment.
1, Java programmers need to keep learning
Looks like this is the most extensive in the industry to adapt, but I can say with certainty: When you are in the web development after a year, looking for work again, you will truly feel this sentence.
First year of work, what are often full of freshness, learn anything, dashing year; WEB industry to update their knowledge quickly, today a new version of the framework, tomorrow is another new framework, it is sometimes based on project We need to keep learning new things; all, very often feel that he used the thing really more than you! But not many really in-depth study of things.
Interview, quit after the first problem is to face; and different interviews with different companies focus; but there is one thing in common: Java is based on the compulsory. First year of work, it may ask you to understand String object is created, and so what is the common framework; the second year of work, they ask you what Java memory allocation mechanism is how the class is loaded, and so on; the third year ask what common design pattern is that you act as what role at work, how to complete a separate module, and so on;
It can be seen ------ This is a typical programmer of the growth process:
Use Java ----> Java-depth understanding of the accumulation of experience ------> independent design analysis capability ------> endeavor rounder!
Therefore, we must learn:
2, open-source framework to resolve
Programmers and code to deal with every day. After several years of basic education and vocational training, most programmers will "write" code, or at least will copy the code and change the code. However, it will read the code is not in the majority, I will read the code and understand the true source of some of the large projects, very few. This also resulted in many wrong ways to see the source code.
3, building the base architect
From architecture design, tuning to the application layer, further in-depth understanding of the underlying principles of solid basic skills to make their own changes to Java sweeping Shenseng: memory model, concurrent mode, threading model, and so on lock details
4, high-performance architecture
We do not just want to make plans for the project, but also be able to solve all performance problems. Only in-depth study underlying principle JVM, Mysql and Tomcat underlying optimization tuning in order to achieve know, know why results. In addition to performance optimization, but also to provide a common point of common thinking and consider the selection of programs to help people cultivate awareness in the program selection, the thinking and the ability to do all kinds of trade-offs.
5, micro Services Architecture
Offs on micro Services Architecture
In the right project, the right team, the use of micro-service architecture benefits will outweigh the costs. Micro-service architecture has many attractive places, but prior to embrace micro services, but also need to recognize the challenges it brings. The need to avoid in order to "micro-services" and "micro-services." The introduction of micro Services Architecture Strategy - For traditional businesses, the beginning may be considered suitable in principle part of the introduction of micro-services architecture to transform the existing system or new micro-service applications, and gradually explore and experience accumulated micro-service architecture, rather than opt for the implementation of micro services architecture.
6, teamwork
Engineering development tools
Building is managed by a short description of the project, software project management tool reports and documents. Programmers fighting, more often than not a fighting man, how efficient deduplication in a single platform, code review, the function to adjust, debug, done under unified planning at every step, chaotic heap code process find their own records. It all depends on effective tools.
7, B2C project combat
Project combat
To the company based on the Internet, and can not be submerged in the wave of the Internet, the project for the development of practical exercise does not have to be a little skill, but also a measure of their ability, and how much there is to equal the number of the rewards. Seemingly simple project needs a map, which is the underlying principle, realization principle can know how much? How much knowledge you build a complete project B2C platform in the end need? All this requires our consideration.
To sum up
1. accumulation of industry background;
Industry background is very important; you must work three years later to determine their own industry background, for example, has been engaged in the telecommunications industry, the Bank has been engaged in the project, has been engaged in the ERP industry and so on.
Can not be a programmer has to write code to write code that also need to know the business logic to meet any demand; Gehangrugeshan the saying goes, every industry, business is different, even very different, for example, you have been engaged in streaming research, so you switched to a bank project, finished, everything from scratch for it, previous industry experience are irrelevant; moreover, a company hiring the company, is hoping to find those very easy to use, no training business for a long time programmer; frequent job-hopping friends, must pay attention to this point;
The industry has been in a long stay, you can become an expert in this industry; we can often see, a leader of a group project, the code is written in general, but it can smooth communication with customers, control of proposed new requirements , bug correction and so on; and customers are willing to deal with him, because those old items only he can maintain his even familiar with each table structure of the system ------- may want to stay in this industry How long time friends.
2. reasonable career planning
What is your short-term career planning is ---- or a long-term career plans! Truths do not speak, we simplify it. To ask you a few questions:
a. You work for years, and you are willing to have new entrants to the novice as it is a simple programmers?
b. You have been willing to write code, I do not care about the others?
Preliminary requirements, design c. A project, post-deployment maintenance, leading to find you, you say we get it working, okay?
Programmers not knock the machine code. The first year do not know too many things, you can all listen to the arrangements boss, knocked code to see the database, and test their code of others; but next year, you still have that right? Impossible, one year of experience you can join, and it is time to learn how to conduct needs analysis, how to design a database, how to write all types of documents, how to write better code? This is a requirement of senior programmer!
What is a senior programmer? Analytical design capability, technical research, but also has a strong background in the industry programmers!
After all, a project to project, you have to actively participate in the preliminary design, the one with the old comrades thinking to analyze problems, learning experience! OK, there you grow it!
Do not think that programmers write code Oh! ! !
Moreover, through the development of a project, you have to be able to rough statistics a function of development time; for example, a module has 20 small function point, you develop 80 hours, each small function point average of two hours ---- - then you will be able to assess the amount of work early. Of course, the efficiency and quality of work of each person is different from person to person, but probably should be able to work out statistics, statistics for the duty cycle of a project;
The ability of the above, at least you have the backbone of a team of friends! At this point, you can lead the younger brother to do the development, rather than being led by a person of ordinary matter.
Many companies are the backbone of the project and project managers are not recruited to come by, are trained to work ------- 2 years, the ability to think good, good hands, it is on the road! OK, this time project managers and mid-level companies might notice you, it will give you more exercise you assign tasks slowly, oh odds this time do not (have met such a colleague, a good technology, people Yes, the leadership of a sudden a lot of tasks assigned to him, he began to silently endure, then it Nao Yixian leader talked with him, he can quite see it over the top for some time on the basic adaptation, can be quickly done;!! later he became our Waiting List in the new project leader is), with people with you to learn, more than labor, it will soon succeed!
If you work for years, it belongs to the veterans, but also good with people, to cultivate the younger brother! Because only little brother grow up, your body burden will be light, the project will be conducted smoothly!
And senior programmer (undergraduate, for example) work about four years wages reached a bottleneck (first-tier cities is 9K --- 1.2W), this time must "transition" ----- just part of your ability of senior programmer , system analysts, architects, technical director is you should tell someone else's job, pay to upgrade again.
3. good attitude and posture
The programmer must have a sense of responsibility! This point is very important. Encounter problems, can not just pass the buck, very careful to communicate with others, made their views, and customer contact, in order to solve the problem. Technical problems is not a problem, always can be solved, but the problem needs to be clear! Once the demand for mistakes, a project may delay or failure. Programmer's responsibility determine his growth, a sense of responsibility could become the backbone of talent, so that the leaders trust!
Second is the ability to withstand pressure, we all know that programmers have to work overtime, stress, all encounter problems must not give up easily, and reasonable based on the ability to deal with!
The body is the capital of revolution, programmers especially important, every day sitting in front of the computer, it is easy to gain weight, become pear body, all the more exercise it!
To some extent, do not quit, at a promising long-term work or work happy to stay it, can not be compared with the enthusiasm of young people, and this time want is steady, the company is acting as a senior IT practitioners to help people optimize procedures, requirements analysis, project ideas to solve problems and so on.
4. write technical documentation
Write technical documentation is a good thing oh ----- fact, it is a summary of your work experience and improve! A willingness to share knowledge with others who, in order to improve constantly thinking! Also, write documentation is training people drop!
It is recommended that wood or blog document often see other people do not write their own peers, it quickly began blogging, fun ah!
(Pay attention to succinct concise technical documentation, providing the source code; summary document focus on personal experience!)
5. With regard to job-hopping
Quit for IT people is definitely not a strange word, almost everyone personally before. First of all I would like to stress that job-hopping and no harm, but the frequent job-hopping on the bad. Before working for four years, you must quit, and encourage job-hopping (recommended experience 2 --- 3 companies); each company to focus technologies are different, not the same control of the development process, the required technical talent naturally not the same; such as outsourcing company, is a code to the madman (I like to recruit people did outsourcing, feeling very many people in the outsourcing company to do things stayed efficiency); small business companies want is an all-around type of programmer (can design analysis, to write code that can be deployed); big companies want is a solid technology, has the potential of people (good English, good ability to understand, Java Jichuzhashi); so if you are in a the company spent a long time, probably modeled on, if once they left the company, it is easy to find a job sometimes run into a wall; and more experience of both companies, is very useful for programmers! And I also have the feeling, each time finding a job in forcing yourself to learn something.
And the key is, once quit, salary even higher ----- many people quit are dissatisfied with the current salary Yeah.
However, once 5 years, it is recommended not to jump in, more are planning their careers, after all programmers are "young rice" is suspect, we can not compare it with young people. If you want to have to do this time technology, it is recommended to stay a long time in a good company, technology + service, enough for you to mix up; if they want the management, this time basically is the time; would like to start his own company, you will have to pay more in-depth understanding of the operations and focus on sales and customer relationships of friends.