New thinking on what programmers should do after 30 and 35 years old.

I have been working overtime in depth this year. Recently, I feel that my health is really not as good as five years ago, not as good as 20 years old. At that time, I didn't go to bed until 2 or 3 o'clock, and I continued to work the next morning, no problem. I feel I can't stand it anymore recently. I am sleepy at eleven or twelve in the evening and can't get up in the morning. If you get up, you will be a little tired in the morning.

I position myself as technology and am not interested in pure management. Technical managers, architects, chief architects, technical directors, if given the opportunity, may be this development route. At present, he is a technical manager and is transforming into an architect. I find that I need to learn more, and my energy is really not enough. There is also a need to change the angle of thinking. You can't think about software from the programmer's point of view. You should stand higher and be comprehensive. You must read (or better do) a lot of things in this field. Think of the system as a whole first, then decompose, gradually decompose and refine it. The most detailed is the programmer's code, which is written by them according to the specification. We should grasp the overall structure, overall design and overall mode.

One more thing, I think it is more important to train team developers. I also found it recently, although we all use object-oriented language. But the code is not object-oriented at all, except writing classes, because you can't program without writing classes. But many times, everyone has not seriously thought about the design of classes, and their understanding is not deep enough. We need to improve our level in this respect. Encapsulation, inheritance and polymorphism are not simple classes. Inherit and write an interface, really. Many times we need to go deeper, and the more the foundation, the more important it is. Still the same sentence: come out and mix, you have to pay it back sooner or later.

The company complains about the slow progress every day, and I wonder why it is slow. I work overtime every day and on weekends, but I can't get up quickly. I am working hard. Nobody is lazy. Why is there no output? I think it is this object-oriented ability that has not improved. When writing code, it got stuck, and the business was clear and the process was clear. I think the code is only two days. Why five days, or something like that? I think the code skills are not enough. How can I improve them? First, think more about yourself and spend more time practicing after work, not just practicing the speed of manual typing, but reconstructing and patterning your own code, thinking about how to improve code reusability and how to keep your own code unchanged. Think about it, and then do it when you have designed it. Only by working hard in this respect can we really improve the development efficiency and reduce the frequency of overtime work. Second, the company should organize training in this field, and spare a day and a half for an object-oriented brainstorming, come up with a few small topics, discuss them together, learn in the process of completion, and exercise their thinking ability and design ability. Third, the specialist will do it. I don't recommend letting programmers participate in business discussion and positioning, because doing business and developing are two different ways of thinking. The development is rigorous and the business is flexible. Fourth, don't let laymen lead experts, it will be miserable, at least the progress will be delayed a lot.

Is this what everyone said about the post-30 s transformation? Is it really impossible to write after China is 30 years old? So I made a thought by the way these days. Found a big secret (haha). I didn't find out why I couldn't write it until I was 30. Why can foreign programmers, many of whom are in their forties and fifties, continue to write? And the writing is very enjoyable. Do you want to transform into management? But management is like a pyramid. The smaller it is, the fewer people it needs. Not everyone can manage, and not everyone is suitable for management. Is there no way out for writing programs? No, this is purely a fallacy of some people, misleading many people, at least I think so.

You might say environmental factors and social problems. Yes, these factors have affected the career of our programmers, but they are not the main factors, which can not be changed in one day or two, nor can they be changed one by one. Just like a revolution, it takes time and human sacrifice, and it needs wave after wave to change.

I think the main factor that we can control is ourselves. As for the saying that writing programs after the age of 30 has no future, it can be explained in one sentence.

Write a 20-year-old program at the age of 35.

How to explain it? In other words, the program written at the age of 30 is still the same as that written at the age of 20, and there is no development or change. This is definitely not enough for a 20-year-old boy. They can work overtime and stay up late, but what can we do? Your body doesn't allow you to do this at all, so it's definitely not enough. The boss thinks that the 20-year-old is better than the 30-year-old. At the age of 20, you can earn less and be fooled more easily. 30-year-old slick is not easy to cheat, and his output is not good. So quit.

In fact, we broke our own back road, but we didn't grow up. When we were 20 years old, we were still writing code and made no progress. There is no progress in code design (not to mention architecture design), so the code written is still confusing, which will affect the whole body. If young people are allowed to change, they can stay up late, but we can't, so they all say that they can't write programs at the age of 30. In fact, the decision is up to us. We should improve ourselves between the ages of 20 and 30. Even if you don't want to do architecture, but just want to write programs, you should write more and more accurately, have your own set, and improve your code skills. Learning design patterns and refactoring, we should consider the structure of the code. We shouldn't write a lot at the beginning and then push it all over again. This will definitely disappoint young people. How can we have energy, right?

You can write a program at will, but you must find a way not to write a 20-year-old code when you are 30, or you will have no future and even go home early, because you can't be a 20-year-old boy.

I hope you are not sad at the age of 30, and I hope you can change. Change this hidden rule.