There is no doubt that a good developer is always learning. It is true that the old technology will eventually be eliminated. But new technology will be out of date one day. So there is no need to blindly pursue the latest technology.

On average, a new standard or framework will be born every 37 seconds, and you can't learn it all. Many new technologies, new frameworks or new features are not necessary for you, and you don't have to understand them. Really valuable technology needs to be polished by the community and the market for a period of time before it can appear. IT companies usually focus on cultivating technologies that suit them, and no company will adapt its code to a brand-new framework. So you don't have to worry too much about being laid off because of some new technologies. What you need to pay attention to is these three kinds of knowledge, in order of priority:

(1) basis. The foundation is the most important. When you master a basic knowledge, you can quickly master its related technologies. For example, if you are very familiar with JavaScript, then any framework based on JavaScript can't beat you. If you master object-oriented programming, you can quickly master a new object-oriented language. Studying the basics in depth can greatly improve your learning efficiency.

(2) The latest version of your common technology. The technology you usually use the most is your iron rice bowl. If they have a new version, it is necessary for you to take the time to learn it.

(3) the technology that big companies admire. If a very well-known company (such as Google, Facebook and Microsoft) releases a new technology and constantly maintains it, then this technology deserves your attention. There used to be hundreds of very popular JavaScript frameworks in the community, but the appearance of Angular and React instantly stole their thunder.

It takes more time to write efficient code than ordinary code.

When you finish running the program and find that the function is realized, you think the work is finished, but it is not. Realizing a new function includes not only writing new code, but also adjusting and optimizing other existing codes related to this function. When you find that part of your time is spent on improving the design of code, you will encounter fewer mistakes in the long run.

In order to reduce errors in the code and optimize the design, you need to pay attention to the following two points:

(1) Prepare the test environment before development. Configure the test function first, and then write the code that meets the test standard. This can not only reduce the occurrence of bugs, but also optimize your code thinking, because you strictly abide by more reasonable and standardized standards when writing code. This will make your code concise and efficient.

(2) Finish the work iteratively, not in one step. Don't spend time perfecting your code until it meets the requirements. You can never make your code perfect. Your first task is to make your code complete the specified function. Usually developers make these two mistakes: either they spend too much time thinking but not enough time to realize it, or they don't spend enough time designing the original scheme. Follow what kent beck said:

Let it take effect first, then make it work correctly, and finally make it more efficient.

Working 7*24 hours won't make you a leader, but reasonable time arrangement is the most important thing.