[Transfer] to technical staff who have just worked

After nine years of work, we have been working on website development for more than eight years. The Team has been in charge for several years. There are also many people interviewing and leading the new job. There are many excellent people, but most of them have some misunderstandings mentioned below. Put forward these questions, hoping to help programmers who have just joined the work, so as to avoid detours.

 

In fact, the most important thing for a company to recruit you is to see that your work ability and attitude are acceptable.

Working Ability means that you can meet their work expectations, or meet the work expectations after training within an acceptable time range.

Work attitude refers to the basic qualities of some employees.

This principle should be clear to everyone. However, in practice, we often get confused. The following are common issues:

 

1. Without testing and Review, I think my work has been completed.

Once your code or application is reviewed by someone else, or you can try it out. At this time, whether your code is good or bad, or whether the function is available in various scenarios, will affect your credibility in the eyes of superiors and colleagues.

Code writing specifications, high performance, and various functions are available in various scenarios, which means that you are completely trusted. The next time a superior assigns you a task, you will be given more freedom to use. In the long run, the future and money are naturally readily available.

On the contrary, the Code is not standard and functions are unavailable in some scenarios. This can only make superiors or colleagues feel that you are untrustworthy. Every time you have to deal with these problems, it is disgusting that you have not wiped your ass every time you pull the stool, and every time you have to get your colleagues and superiors to help you wipe your ass. After this is done several times, the superiors or colleagues will feel that you are untrusted when they communicate with you next time. One thing must be emphasized multiple times, and you will always feel that you are still making problems. Your credit is already very dangerous.

Your credit in the eyes of others has been drawn by you slowly. To a certain extent, leave. The efficiency of the entire team will slow down because of you (the cost of communication between everyone and you will affect his own output.

 

2. minimum acceptable work time limit

Have you ever made statistics on how long the Work Plan assigned to you by the company is estimated to be different from your own expectations?

If the estimated time is longer than the work plan time provided by the superior, and the superior does not have additional personnel to do the work. In addition to the BT leadership, there is only one situation: the superiors are very dissatisfied with your work attitude and think that your salary is not the same as your work ability.

For new jobs, more is that the performance of your work is under the average work ability of the company. At the same time, the company feels that you are not enthusiastic about your work. Where is the future of a person with a lack of ability and passion under average ??

If this person hasn't shown hope that he can reach the average level in a few months, why should he leave such a person?

 

3. working ability is not equal to technical level

I have seen some people complain that the employees of large companies are just the technical level and there are no such simple technical problems. I had this idea in my early days and later found it wrong.

Whether large or small companies, they must be able to solve problems. I once had several excellent technical skills, but the applications I made were reworked again and again. Why? They are not doing well for non-technical factors such as ability to work.

There are many non-technical factors involved in work ability: responsibility, performance is to have a reassuring Responsibility for the code you write; communication ability, A typical manifestation is that when the demand is not understood or the demand is unclear, you must communicate with the relevant person in a timely manner, instead of implementing it based on your own ideas, resulting in the consequences of rework after the code is written.

I have met some people who have low technical skills but strong problem solving skills. The ability to work is more important than the technical level. It is easy for technicians to have a high technical level, but the non-technical work ability is poor. This is terrible.

 

4. development potential and learning ability

The technology used by the company cannot remain unchanged, and the company that remains unchanged can only be gradually eliminated by the market. This requires employees to constantly learn new knowledge and apply it to their work.

If you don't want to appear for a few years, you will find that no one wants to find a job after job hopping. study now.

Persistence is the most difficult thing for a person to do. But if you don't stick to it, wait for the destruction.

 

 

5. Stupid birds fly first

If a person is in the company and his or her work ability is below the average, work overtime. Don't have any fantasies.

The most terrible thing is that you do not have this consciousness. You think that you are a good technical skill, but the ability to solve the problem is below the average level, with a low eye. Such a person cannot stay in the company.

 

 

6. Make sure you do what you promise. Do not find reasons.

If one thing is not completed, you can find a lot of reasons. Since you promised to finish it before a certain time point, you should not shirk it for any other reason.

Although the company's colleagues and superiors may have accepted your reasons this time, the next time, it will gradually make your superiors feel that you are a person who prefers to push your back. I feel that you are very unreliable. I don't know if it will be completed at that time. Who will try again next time?

 

Newly Added:

7. If you are competent, you do not need to work overtime.

From the CSDN comments, the most controversial one is overtime. I would like to add my views on overtime.

First, everyone must work overtime. This must be the responsibility of the leader. The overall work progress is under too much pressure.

Continuous continuous overtime is also the responsibility of leaders, and people cannot stay tied up.

However, if a department is working overtime for some people, some do not work overtime, and it is not because the leaders are mentally retarded and assign more people to work, but some do not. A person who works overtime can only show that his or her work ability is under the average of the Department.
For the same job, if employee A does the job for three days, then employee B does the job for five days. In the end, if the job is assigned to employee B, it may be four days for him to complete. And he must work overtime consciously.

This is what I said: A competent person does not need to work overtime, and the ability to work overtime consciously under the average.

 

 

Many people may think that I am very mean when reading this blog. It seems that I am bullying technicians from the company's perspective. Very humane.

As long as you are not a director of the company, you will always be stripped. The company's goal is to maximize profits, which is the fundamental purpose of the company's survival. As an ordinary employee, white-collar awareness is actually exploited. This is an ecosystem for the survival of the fittest. unsuitable people can only be eliminated.

The actual company has a lot of human feelings in it, or it is difficult for colleagues and leaders to say something. This also caused some technical staff to be dismissed. What do you think? These are all caused by lack of consciousness. I am writing this blog to increase the awareness of the technical staff. I don't know what to do if I do not commit these problems.