Thirty fame and fortune-a Senior Programmer's career

The author has been working as a programmer for more than thirty years. During this period, he realized some truth. For example, success came from the summary of failure, and he learned a great deal from Rome, rome doesn't care how you get there. What experience have you accumulated in your life? Share with us.

I have been working as a programmer for more than 30 years. I have learned something and want to share it with you here:

Customers do not know what they want.

The presentation of a functional prototype system saves unnecessary and inefficient details.

Any security measures are not safe as long as enough time is given.

Security is a major challenge for system O & M. Every moment we try to protect our systems and data. However, once a hacker succeeds, all our efforts are very likely to be lost.

The impact of the system after it is cracked depends on preparations in advance.

If you can estimate the consequences of the failure of the protection system in advance and make full preparations, such as separating key data from storage and encrypting the data, it may reduce the chances of making headlines in the future.

Good security deployment is not just an overhead, but a strategic asset.

At work, I always hear people often complain about how complicated and expensive security O & M is. Therefore, some enterprises often find themselves saving money at the expense of security, at last, I had to swallow n times of bitter fruit.

Complex problems are much more complicated than common problems.

It is a common phenomenon in any field of creative art, such as programming and design. I will try my best to make the code simple and easy to understand, whether for myself or for others. If you want to show your smart talents and deliberately make the code complex, maintenance will be terrible. Of course, from the perspective of protecting intellectual property rights, this is understandable, but it may lose the vitality and creativity of open-source software.

Success comes from the summary of failure. If mistakes are repeatedly tolerated, failure and success are destined to be two parallel lines.

When people get used to their mistakes, they may create valuable products. We need to set a goal: only allow ourselves to make the same type of mistake once. Only by strictly controlling the frequency of errors can we continuously improve the software development level.

What remains unchanged is change.

It is unwise to plan tomorrow based only on the current situation. Especially in the world of programming, there is no permanent dead path. It is doomed that we will not succeed if we refuse to accept or try new things because we are opposed to technological advances and keep ourselves closed.

Lifelong Learning

One of my favorite sayings is that we all follow a big roller behind the scenes. If we just stop a little, we may be able to drive people around. Therefore, we must run faster than it, keep moving forward. When we believe that we have mastered everything, we do not know that it is actually the beginning of a regression.

The entire software industry is filled with wild arms

In ancient times, if the precognition fails to predict, it will kill the stone. Now, even if the prediction fails, the experts can leave the whole body, instead of making another prediction. As a result, the wild donkey conjecture is prevalent, and everyone likes to predict the conclusion. This is an impetuous age.

Rome does not care how you get there.

Customers don't care about what problems you will encounter. They just want your software to solve their problems. System downtime, hardware damage, and hacker attacks are of little interest to customers. It is a good practice to tell the truth about these mistakes, especially before the customer knows how to solve them.

Customers are the best quality standards

No matter how many measurement indicators you have, how many back-to-code reviews and how many acceptance lists you have passed, these are actually secondary. The most important thing is that we achieve what the customer expects, nothing is useless. Remember, the customer is the final QA.

No record, failed

Today, I still think that if people do not collect logs, crash reports, and other useful information, how can they stay. What I have always insisted on is to record as detailed as possible, track crashes, read review reports and remarks, and quickly locate errors.

Although there is a better way, the time will not stop waiting for you

The most difficult part of the evaluation is to strike a balance between termination and continuation. If it is terminated, it may lose the opportunity to find a better solution, but if it takes a long time, it is actually not very valuable. This is a difficult choice, but sometimes the quick choice made today will be more effective than the one that will be made next year.

Find rich gold owners

I was impressed by the idea of a sales person I once worked with: finding someone who doesn't know the technology but has a lot of money is like finding a large gold mine. Smart people may ask too many questions. Poor people cannot reward you. I sincerely feel happy to be a programmer!

My job is to lie to customers. Your job is to make me look good.

As the salesman, he prefers to verbally promise the customer to complete the impossible tasks. After we finish the tasks, we will first get our rewards and praise. Although challenges and difficulties can be fulfilled, every side effect is endless pain. My suggestion is: Find another better sales as soon as possible!

Thirty fame and fortune-a Senior Programmer's career