Reposted others' good learning and accumulation Methods

A wide range of knowledge, and can always supplement your knowledge and improve your knowledge structure.

Good patience, especially in the debugging and learning stages, there are no smart people in the world, only hard-working people. Development involves learning and making mistakes. The development process between these two things is actually relatively simple.

Always remember: code is for people rather than for machines. Computers are not afraid of fatigue when executing programs, while people are very tired when reading code.

Good coding habits, at least ensure that you can understand the code you wrote a few months ago at any time.

Try to make your code easily understood by others. When writing code, think about whether you will be scolded by others two months later.

Do not tolerate repeated mistakes and repeated code writing.

Knowing how to do it is more important than getting code.

Do not do things that many people have already done.

Learn to respect others' development achievements, unless you have to decide not to fully replace the previous system.

Cherish your time and work achievements and try to share your development achievements with others.

Avoid assumptions, think more about extreme situations and the possibility of errors, and try to reduce low-level errors.

Do not trust at least the test results you have made for yourself.

Learn how to stick to your own development ideas and understand and absorb others' ideas.

Learn to be consistent with others, but do not give up on your development features.

Learn from people around you, whether in terms of development capabilities or development experience.

Understand the importance of the software structure and analyze the code structure before analyzing the code.

Learn to sum up and summarize the knowledge you have learned on a regular basis to see the time you have wasted for various reasons.

Learn to plan and try not to think that you can complete the task by extending your work hours.

Learn to estimate your abilities and working hours correctly.

The following are some of my ideas that suit me, not necessarily for everyone:

Read more magazines. If you have nothing to do, you can look at the reference books you have read before. The book may have some details you have not noticed before.

Do not do something unrelated to development too early, because the golden age of learning is very short.

Learn to analyze others' systems and look at the advanced aspects of systems developed by others. This includes others' development ideas and structures used for implementation.

I often feel that I will be eliminated, and I often complain about my lack of efforts.

Know what you are missing.

Force yourself to do something you don't like, such as writing documents.

You have the courage to rewrite your system, but when you redo it, you should adopt a different way of working and method from the previous one. Otherwise, redo is unnecessary.

Simplify the problem rather than complicate it.

Resolve part of the issues that may occur during maintenance during development or design.

Sometimes you may also ask yourself: What do I do when I do not do development.

Keep Developing weekly plans for yourself, and do not shift your attention before it is done.

Teach others as much as possible, because one day you may not be responsible for this system.

You must start and end your work. Do not leave before your work is completed unless you have any reason to do so.

Do not take away what you do for the company, because you should take away development experience and understanding of development rather than code and products.

If you are tired, just take a break and give yourself a vacation. After all, people are not machines.