New thinking about how programmers will do after 30 years and 35 years of age

First of all, I wish you a happy holiday.

I this problem seems to have a bit of "menstrual paste" meaning, but feel more than the language of the menstrual paste has more value, at least be considered, life guidance, pilot it.

Several days did not write a blog, we will also find that some time ago I write a day, are in the evening or in the morning to write. In the last few days I feel like I'm going to take a break. Why, then? I'm only 30 years old, and I don't have enough energy. Of course, the World Cup is a factor.

This year has been working at a depth of overtime, and recently felt that the body is really not as good as five years ago, as well as 20 years old. At that time to learn to 2, 3 to sleep, the next morning to continue to work, no problem. Recently feel to boil, the evening 11, two point on the sleepy, the morning is not up, up words, a bit of energy in the morning is not enough.

I'm positioning myself as a technology, and I'm not a fan of pure management, technology managers, architects, chief architects, technical directors, and if there is a chance, it may be the way forward. For now, it's a technology manager who is turning to the architect and discovering that there's more to learn and less energy. There is the angle of thinking to change, not to the programmer's point of view software, to stand a bit higher, to comprehensive, they have to see (preferably done) a lot of this stuff. First from the whole to think about the system, and then decomposition, step-by-step decomposition, refinement, the most fine is the programmer's code, that by them to write in accordance with the norms, to grasp the overall structure, the overall design, the overall model.

Another thing I think is more important is the need to train the team's developers. I have recently discovered that although we are using object-oriented language. But the code is not object-oriented, in addition to writing class, because do not write class also have no way to program AH. But most of the time we have no serious thinking about the design of the class, and the understanding of everyone is not deep enough, it is necessary to improve the level of everyone in this respect. Encapsulation, inheritance, polymorphism, is not a simple class, inheritance, write an interface, it is really the case, many times we still need to go deeper, the more basic the more important. Or that sentence: Out of the mix, sooner or later to return.

The company is complaining about the slow pace of progress every day, and I'm thinking about why it's slow. Every day in the overtime, weekends are also working overtime, is not fast up, are very hard, no one lazy, why did not output it. I think it is this object-oriented ability to improve, write code when stuck, business clear, process clear, think the code is two days, why 5 days, or almost. I decided that the code is not enough to create, how to improve it. One is to rely on their own more thinking, work more to spend some kung fu practice, not simply to practice the speed of hand-tapping code, but to their own code refactoring, mode, thinking how to improve the code reuse, how to make their own code is not changed to change it, to do before thinking about, design. Only in this way, can the real improvement of development efficiency, reduce the frequency of overtime. The second is the company to organize this training, take a half-day time, to an object-oriented brainstorming, a few small topics, we discuss together, in the process of completion of learning, exercise thinking ability, design ability. Three is a special person to do. I don't recommend engaging programmers in business discussions and positioning because doing business and development is two different ways of thinking. The development is very rigorous, the business is very flexible. Four is not a layman to lead the experts, will be very miserable, at least the progress will be delayed a lot.

Is this what everybody says after 30 years old to change? After 30 years of age in the country really do not move it. So these days by the way to do a thinking. Found a big surprise (haha). I found out why I can't write at the age of 30. Why foreign programmers, many are 40, 50 can continue to write it. and write very enjoyable appearance, we need to transition to management. But management is like a pyramid, the more the smaller, the need for fewer people, not everyone can do management position, and not everyone is suitable for management. Is there no way to write a program? No, this is purely a fallacy of some people, misled not to know how many people ah, at least I think so.

We may say that environmental factors, social problems. Yes, these factors are affecting the careers of our programmers, but they are not the main factor, and these are not a day and two days can be changed, and not one of us can change, like the revolution, need time, need people to sacrifice, need to build up to a certain degree can change.

I think we can control, but also the main factor is our own. The argument that there is no future for writing a program after the age of 30 can be explained in a sentence.

30 (35) years of age to write a 20-year-old program.

How to explain it. The 30-Year-old wrote the program or 20 years old when the appearance of writing out, no development, no change. That must but 20 of the lad, they can work overtime, stay up late, but we do, the body does not allow you to do so, certainly not. The boss felt that the 30-year-old might as well be 20 years old. 20-Year-old can also be less wages, better fooled, 30-year-old old fried dough sticks, not easy to cheat, and output also die, then quit it.

In fact, we have broken their own bridges, is that we do not grow, but also in writing 20 years of age to write code, no progress. There was no improvement in the design of the code (and not the architectural design), so it was written in a rather confusing, far-reaching code. If we let the young people change, he can stay up late, but we are not, so we said 30-Year-old can not write the program. In fact, the right to decide in our own, to 20-30 years old, to upgrade themselves, even if you do not want to do the structure, just want to write the program, but also to write more refined, to have their own set of skills to improve the code. To learn design patterns, refactoring, to think about the structure of the code, not one to write a big throw, and then pushed to the back, so sure but young people, which have that energy ah, is not it.

Just want to write a program can also, but must find a way, at the age of 30 do not write 20-year-old code, otherwise there will be no future, and even go home early, because you do but 20-year-old boy AH.

I hope we do not feel at the age of 30, I hope you will make changes. Change this unspoken rule.

I am sure there will be a lot of people in favour of this point of view, and many people will oppose it.

Finally, to ask everyone a good, happy holiday.