Quick is the main theme of today's work. When you get the task, you will be able to achieve the goal. You can even process multiple transactions at the same time. Once you are idle, you will feel a lack of presence. This is not necessarily a good thing. It is relatively simple to do, and experience cannot be effectively accumulated. In the end, it is still not fast, but it is still restrained by work. Compared with doing things right, I prefer doing things bigger.
From the surface of a task, it is result-oriented if the result is finished. If you want a report, I will give you a report. To solve a bug, make sure the bug is normal and there is no problem with expansion. If it is really urgent, it is a matter of course, it is not appropriate to slow down. But if you have the opportunity (
You can confirm through the above discussion. If you don't have time, just squeeze it yourself!), And try to let yourself slow down, take a good look at the system, overall thinking, and try to understand some details. That is to say, in addition to solving problems, what improvements can be made and what changes can be made to products. In short, if you have the opportunity, you must try to slow down and make things more extensive, in-depth, and systematic. For example, when you do one thing, you must first prioritize and then understand the objectives and objectives of the task.
For example, if you encounter a page development problem, it can expand many dimensions. If you have time, I like to start with the following method:
Target is to solve specific problems. Objective: To improve understanding of products and codes, avoid similar problems, and improve product quality.
1. For the functions of this problem, first understand the main classes and processes of this function.
2. check whether there are any standards or norms for this issue. If so, read the standard definition of related concepts roughly.
3. How did others do it? Compare the functions of similar products. Write some test pages for verification.
4. What are users' expectations?
5. Formulate a solution at the system level, rather than simply discuss the problems to be solved.
6. How to avoid similar problems? How to verify the problem?
7. Do I need further understanding? Is it possible to make some innovations? Is there a chance to apply for a patent?
This is the way to think about things as much as possible at work. Even in the face of a bug, we need to explore the space for further optimization and innovation. In fact, only by going deep into the details can we have more opportunities to Discover Opportunities for optimization and innovation. We don't need to rely on a large project to improve ourselves. Because of the continuous refinement of technical work, it is more effective to promote learning improvement in the form of a small learning group, and the large scale of technical training income is very low. Furthermore, personal learning is the most effective, but this habit needs guidance.
At present, the value of work experience is far less than that of learning ability. Focusing on improving learning ability is far more valuable than focusing on what projects are involved. In our work, we must focus on the results, pay attention to the process and method!
Reprinted please indicate the source: http://blog.csdn.net/horkychen
It slows down the pace of work, and can make great achievements in simple work.
