What you lack may not be ability, but a rematch.
Every year at this time, in order to feel the ritual of life or KPI, they begin to prepare their year-end summary. To sum up the year in a few words:
What did you do?
What was the success?
What did you get?
What will the future do?
Or out of the growth of the need to sum up their hard work for a year of firewood, rice, oil, salt, sour, sweet, bitter, hot. Or out of the company’s demand for KPI, write a summary. The difference is also due to the purpose, whether it is for the need to raise salary, or for the “lead”/KPI team, or to reward themselves. Different destinations, different things to write, different harvest. Things written for work don’t always help you so much — they’re always focused on work. Their approach, which is largely results-oriented on a yearly basis, is fraught with unsustainability. They are no match for five-year, 10-year personal goals.
What do we care about?
The humble and the noble, the beautiful and the ugly, the young and the old, in sickness and in health, I always write a year-end summary to myself. Plus certain decoration, beautification, it will be out in the open. Either to gain a sense of being watched, or to remind oneself of the truth ahead, on the one hand, mostly to gain approval. And this kind of summary, according to their own point of view, often have such some routines, or mode, or template. There is no need to distinguish between the three, they have a core content: what do we care about? . In terms of skills, I care about the following skills:
Programming.
Writing.
Design.
Look at yourself: technically, what improvements have you made, what wheels have you built, what could you have done better? In writing, what have you learned? What books have you read? What articles have you written? Do you devote enough time to your art, and are certain aspects integrated with your work?
It’s the elements that figure out how to focus on what we want every year and keep correcting ourselves.
1. Write a “chronicle”
As a first step, I like to list what I have done on a yearly timeline. This approach seems to turn the year-end review into a running tally, which seems pointless. But its purpose is, on the one hand, to avoid missing something important, so that it can be summarized later; Second, often many small content, may constitute an effective result.
If we were a robot, with little effort, we could figure out how much time we spend each day, where we spend the majority of our time in a year. Unfortunately, we are not, we are just ordinary body, even the slightest physical discomfort, can affect our behavior, thinking speed. Almost every day is completely different. But that’s not how it looks to us. Our workdays look the same:
Get up – > – > work – > eating lunch – > lunch break from work – > work – > – > – > hobby – > you have to sleep
In these mundane, we need to list, this year did what important things? According to the model of different companies, they are listed in different ways:
For example, in my work, I need to count what I have done in different projects by project.
For spare time study, GitHub projects are used as the unit of statistics
In general, on a monthly basis, to list what you do, will be more detailed:
In January, blabla
In February, blabla
…
Combine the dimensions of our concerns with “bills” and you have a rudimentary version of the year-end report.
Write these things down so you can summarize them.
2. Look for key results
Whether it’s an internal year-end report or a summary for your own review, distill the most important parts of it. Just like writing resumes, a good resume can highlight a certain part and leave a good impression on HR. A bad resume, on the other hand, will look flat — because the person who wrote it probably sees everything as important.
This section is like looking at KPIs. Where it is done well, it is where it can be harvested. If something is not done well and results are not produced, nothing can be done about it. This is why a self-summary is needed — taking KPI as the starting point will ignore my own growth. Kpis don’t necessarily recognize what you’ve learned this year. Because it doesn’t have any value for your learning at the moment.
From our ledger, find the bright spots, the achievements, that we need to show off, prove our worth, and inspire us. Or put it on your resume and look for opportunities at your next job. Such as:
During this year, I wrote a micro front-end related ebook and wrote a micro front-end framework, both of which received a certain degree of attention. The former has 550+ Stars on GitHub and the latter 250+ stars on GitHub. Numbers + results, all let a person feel happy.
If it’s because you’re doing something mundane, don’t be too ashamed, but look for the key results. If we lose track of what is important to us, or what is important to us, it becomes even more important in the coming year to be aware of whether we are not learning anything new, or whether we are not in the right place to use our talents. If you can’t learn something new, you will be afraid of a crisis in the future, so you will make yourself more anxious, and then take action.
Write these things down as milestones.
3. Summarize your gains
The purpose of the year-end Review is not just to share with friends, but to allow yourself to Review your performance and decide what to do next.
Summary is a written material used to review and analyze the work of a certain stage or the completion of a certain work, including achievements, existing problems and experience and lessons obtained, to provide help and reference for future work.
It is my habit to separate successful outcomes from less “successful” ones. I always feel that some part of the results, as if taken for granted. But for successful projects, for successful results, I wouldn’t say there’s nothing to learn from it.
In some things, the success part is more difficult, you can learn something. Because in the process, you or someone else stepped up to solve a problem and normalize the whole thing. Then it will be easy to see what everyone likes.
And some failures, it is doomed from the beginning, such as the pie is too big to digest. Most failures, however, are not, and they deserve our attention. For us at present, the results of some things are not within our power, and some are beyond our ability. For example, we put a lot of effort into writing an open source project that had no users at all. Whether there is a bug in the application, or any lack of operational capability, it will show up to some extent.
So, in any case, we have to look for reasons from it, in order to facilitate their own learning. Summarize your thoughts and try to solve them the next time you encounter them.
Write these thoughts down for future comparison.
4. Improvement plan and purpose
And then, from the bits and pieces of the past, we will continue to gain knowledge:
Since you know why success, then you know how to learn success, summed up the experience and model
Since summarize why the failure, it is necessary to analyze the improvement plan
Then all we do is set a goal and create a plan. Or create a goal and plan for improvement.
But not all goals need to be achieved. There are different levels of goal classification in different ways (typically the MoSCoW prioritization method), or as the author is accustomed to:
I Must have it.
Nice to have, but not to have.
Some things in this life, one year to do next year; Some things will be better next year. Figure out what your priorities are, and then plan for them.
Write down these goals so we can change our plans.
5. Plan
Both learning and implementing plans are as follows:
State of mind.
Skills.
Tool.
Depending on the target, there are different ways.
In addition, for those who are learning C/C++ programming or want to get promoted at work, if you want to improve your programming ability, help you improve your level! The author here may be able to help you ~
Wechat official account: C language programming Learning base
Share (source code, project actual combat video, project notes, basic introduction tutorial)