Mentioned update your resume, perhaps the first time we thought of changing jobs, because updated only when changing jobs. Programmers usually about a year and a half to two years to quit once, that is to say up to 2 years will be updated.
Update your resume is one in which to update their technology and to show for all kinds of highlights, so from a sense, was updated at least once a month, after a month no progress somewhat justified. Generally speaking, there are the first technical update and then updates on the resume.
1 Why do you want to update your resume?
The first course, in order to find work.
The second is to undertake private life. Such as looking for publishers to find video sites, looking for training school, find a partner, generally need to show their ability and background.
The third is to record their growth, such as through the project practice, familiar with the dubbo retry and failover mechanisms such as the principles and underlying implementation details, then it can be coupled in Dubbo technology used in the list at least, can write more appropriate, on "familiar Dubbo underlying implementation" and other words. This of course can be unified together before changing jobs, but may not be able to write full-time, so it is recommended to add a progress.
2 small update weekly, if not update, you have great importance
The Analects of Confucius, there are three times daily to say, so we can conclude that progress can be updated at the point of the week every week.
Why is a small weekly update? First, although there is progress every day, but the magnitude of the extent of progress may not be able to update your resume. We know that the resume is to look at the company, it is not on the table a number of points on the progress of self-deception. For example, we can not write "xx chase drama set how much" or "xx game to what level" kind of thing. So small weekly updates What should you write it?
The first point is technological progress, such as I am familiar with the SQL statement tuning skills, you can write "master plan by indexing or tuning execution skills' experience in project described in the corresponding.
The second is the understanding of the framework, such as the familiar practice of MyCAT, you can write "with the MyCAT" or "familiar MyCAT" kind of thing depending on how familiar.
The third aspect of the project, such as just this week are familiar by jenkins deployment project, you can write "will use (or familiar) jenkins automated deployment" skills.
Fourth, the other can prove their highlights, this is not limited to the technology, such as in the garden write a blog post to stay in the home, or send a high traffic article published in a public number where you can write " there are technical blog, and there is a certain amount of clicks "like words.
When the time is updated weekly, can record running account, you can record more details, here for example, such as recording your own experience high concurrent Java, it can be listed on all points, such as thread pool, CountDownLatch and all the familiar points, so to reflect their progress.
During the operation, if this week is really busy because of work I had to do duplication of effort, yet it excusable, but not for long, because if not updated for a long time, it will only allow themselves to be skilled workers. If for personal reasons, then you need to pay attention, because no progress this week belong to no reason.
Or some students said, this week, last week and progress to the same technical points, such as this week is to continue the practice of re-tuning the database, although the same general direction, but does not necessarily point this week and last week's agreement, which updates the point . Or have students will say, I usually work really duplication of effort, so the type of work this week and last week, are doing CRUD operations. However, certain items included in the middleware technology, but must also components with high concurrent load balancing and the like, you can find a way to become familiar with the practice by class skills when the project deployment. In short, this week's review of the way, we can Forced continuous progress.
3 large monthly updates, induction or progressive system-level framework
Small weekly updates, you can record running account, and large updated monthly, we need to be aggregated into these fragmented system-level progress.
For example, in this month, fragmented record of progress in terms of high concurrency, then in the month, you can get rid of the points, summarized in one sentence: familiar (or proficient) thread pool (or other knowledge).
Or in this month, saw a lot of the underlying code in Spring Cloud Hystrix part, have a certain understanding of the current limit and retry mechanism, it can be summarized in one sentence: Hystrix familiar with the underlying code.
When large monthly update, or can not find a summary of the progress of scattered point, it shows progress points too complex, too much emphasis on applications, no dig deep from the underlying code or implementation mechanism, then you can correct the direction of their progress. Or find their own progress too theoretical point, then later point of time, we should find more opportunities for hands-on, such as in the project team in the allocation of living, and more would like to see and do more.
Four pairs of some projects lack the experience of the students, but also need to find ways to update project experience
For example, junior and senior students prepare to find a job, or working less than one year, the practice of project experience relative lack of crowds, I was doing when the interviewer technology, mostly just to see the description of his experience and expertise on this type of resume, basic rarely see a decent commercial commercial projects, which led to such a resume is not an interview.
Pro Yuan Xian fish, as retreat webs, expected to be found in the lack of project experience with a resume, might as well think of ways to give yourself a chance to practice more projects, of course, the project can not be false.
1 For example, in the school stage, the teacher will have a computer and often out of contact, if not college lecturer with a master teacher will always be, we can own and related teacher contact, or introduced by others. Do not think they can not afford so the teacher will not be, in fact, the beginning of all this, a good attitude point and then took the time, and soon will be able to work.
2 school stage, and even can go out and find some software companies doing internships or part-time, beginning not for money, but to project experience.
3 graduate design course design projects have completed the work, although not a commercial project, but better than nothing, of course for those projects, not to mention, there is a natural teacher will guide how to write.
Above is the way to find project opportunities, with the opportunity to worry about the project can not be updated, and when some of the students friends, you lack experience in project sigh resume, whether looked efforts got the idea? Or is this sentence, do not wait.
The students started the job, the project may experience less time, and that can put the things you have done are listed on, such as to help run test cases, deployment projects, do front and back end development. In short project experience to look very full, which fully reflects your practiced skills, so your resume can help you get more of the interview.
5 apply what they learn in the course, continue to work hard in the correction direction
Can resume our growth record, more Forced our progress, but more should we drive revenue. For example, in different scenarios, showing different emphases resume. For example, the application of different positions, can be described as fine-tune your resume according to different positions.
Meanwhile, in use, often find themselves trying different direction, for example, I recently distributed components intend to record video, but in the resume and match specific requirements, most of which are found to experience, but a shortage of more in-depth experience in terms of principle so I can promptly adjust direction.
And I'm in the interview, found that many candidates on a resume are mostly too basic skills, such as databases simply CRUD, and the lack of more in-depth tuning experience, and experience too much focus on windows, linux aspects very scarce. Regardless of whether the candidate through the interview, I will be to them. But then again, even if I do not explain, after interviewing candidates should be aware of this, efforts to correct direction.
6 Summary: Update Your frequency is equal to the speed of technological upgrade
In your resume to help you fight for the opportunity to do an interview this blog, I told tips on how to optimize your resume in the current project technical background premise. In this article, it is from the source, about the method of updating skills and update project experience. Rich project experience, skills upgrading, and resume naturally more valuable, and that naturally enhance revenue.
Moreover, the paper also focuses on a point of view: Do not wait for opportunity, but by the fight, such as multi-win project experience in school, after work experience of fighting for the skills of the project group. And the consequences can wait to make their resumes for many years did not update point, so that their income is below average.
If you feel this article helpful, please recommend this article, also welcome to exchange through the comments.
Copyright statement:
There are a lot of friends and you want to reprint reprint my blog, I am very honored, and this is I constantly write power Bowen. Copyright of this paper are as follows uniform, sorry not reply individually.
1 This article may be reproduced without informing, please use the reprint, link the way, given the original source, do not simply given by the text, while the original author is stated hsm_computer.
2 in the reprint, please reprint the original, declined wash draft. Otherwise, we reserve the right to pursue legal responsibilities.