Turn around-not just developers

Turn around-not just developers

On the way of life, we often face a lot of choices. Sometimes, for some reason, we have to give up some previous ideals, change our thinking, and make a new choice; this is also true for careers.

 

The topics in this article are as follows:

No silence, treat yourself well

Change yourself and take the initiative

Technical trade-offs

 

No silence

In the eyes of many people, developers are "silent": They do things silently every day, work overtime on the tasks distributed above, and everything goes against it, hiding unhappiness in your heart is often an image that is unsightly... some people even think that development should be like this. Only such personnel can be regarded as developers.

Once, it was brainwashed by the so-called "silence. Desperate "Silence" to do things. Later, I looked back and found that I knew nothing except technology. Life is not only about technology, but also about technology. In addition, there are many things to know: for example, how to communicate with people efficiently, how to deal with all kinds of people in society, how to manage yourself and others, how to deal with your work and family, and how to turn the real business into something that can be achieved by technology, how to control the global ....

Technology can be said to be a hard skill. You can learn it, and others can also learn it. You can do it, and others can copy it. But the mind and way of thinking for people to do things, as well as the business and management minds that have been developed for a long time, these are soft skills, and it is difficult for others to copy. Maybe this is your core competitiveness.

Developers are neither machines norCodeThe generator that stores itself on the computer all day long, and may not become an expert. In fact, programming technology, object-oriented, and other ideas come from life. From the perspective of life, we can use the way of thinking in the programming world in life to bring the two together.

There is a saying: competent people will do things, but smart people will let the competent people do things for themselves.

 

Change yourself and take the initiative

Many times, we place ourselves in a small circle and don't want to go out. Always think: there is always something someone will do. This is also the case during development. If you have any problems, you can defend against them. If you have any problems, confirm them above. do not develop this kind of "inertia ". What if you had to go there that day? Maybe we are still a developer, or working for someone else. When I start my own business, I want to discuss and negotiate with the customer, and I want to compete in the market and raise funds with others, what should I do?

The society will not wait for you, and the opportunity will not wait for you; sometimes, it is necessary to make a shot when it is necessary to come forward, even if it is hard to scalp, maybe this is your chance to turn over in your life.

 

Technical trade-offs

The mastery of technology is not only always at a small level, but also should not be the same as the dead syntax or the difference between new and virtual. I do not deny that the basics and details are important, but the technology should be"Go up or down".

The so-called "Go on ":

How to select a technology for a project? Why? What technical difficulties will emerge when the demand comes out?

How to structure, how to deploy, and the development of the project in the future. In addition, if the project has requirements on security, stability, and performance, how can we provide feasible solutions in the short term and long term. For some Internet product projects with millions and tens of millions of users, how should we consider looking for future situations during development and design ....

The so-called "coming below": how much detail is learned about programming (including syntax and common class libraries), and whether each line of code can be further optimized. After a piece of code is executed, what are the requirements for CPU, memory, managed resources, and unmanaged resources? How to manage objects and know when to release objects.

 

I have been busy recently. Now I am taking some time to talk about it. I hope you will not be surprised!