Why programmers in China are generally at a low technical level

First of all, a Senior Programmer is not able to practice by reading tens of thousands of lines of code on his own. I am more concerned with the low-layer environment, that is, the real working environment of programmers. Because the programmer's level has to be measured from the actual work, not the other. So what I want to say is that the nature of Chinese software companies directly leads to the level of programmers. The software company I mentioned does not refer to one or more software companies, but to mainstream software companies and public software companies. So I hope programmers who have entered an ideal company can understand the position of my article.

Impact of unpaid overtime work by software companies on programmers:Programmers in domestic software companies often work overtime, daily addition, and weekly addition. Based on this nature, there is a very inexplicable phenomenon: the actual off-duty time of programmers every day is always later than the specified off-duty time, as for the last hour or two hours, the programmer feels like a thief if he gets off work on time. On the surface, the company has not forced anyone to work overtime, but in fact there is a deterrent in the subtle sense that you need to work for the company for a few hours, on the surface, you have been willing to work for the past few hours. Because it is "self-willing", the company has more reasons to think it is free of charge.

Another reason is that the week does not work overtime. Generally, the week does not work overtime because it is "busy" (for "busy" with quotation marks, see "the influence of" busy "of software companies on programmers "). However, weekly overtime work is generally free of charge. As for the "compensation" stipulated by law, it is even worse. However, the general company stipulates that you can take a break if you have not worked overtime for weeks. The shift is generally due to the addition of weekly and non-weekly shifts, but the shift is far away. The reason is very simple. The company is "busy!

The impact of this situation on programmers: Negative, weak, unassertive, hypocritical, and unpromising.

The impact of a software company's "busy" on programmers:

In fact, software companies are sometimes really busy. For the reason, software companies think it is caused by programmers (there are actually other employees, but this article does not involve discussion, what Programmers think is caused by the company. However, according to the principle that the company is not busy, it should be caused by a vicious circle of uncoordinated cooperation between the company and programmers. For deeper reasons, you can study it yourself. However, from the perspective of my appearance, there are several "busy" points. If these points do not represent your opinions, you can add:

• Project development and planning are out of touch, showing that project development is slower than planning.
• Unexpected events.
• For some unknown reason, such as the show.
• Fake busy.
• Really busy.

The first case mentioned above is the most common. This involves the software engineering topic. In fact, it is also the core of software companies that do not do much, and the programmer level is not high. "Software companies are not doing big" has been the predecessor's article: Why can't domestic software companies become bigger and stronger?" As I said in this article, "the programmer's level is not high." That's why you have read these two articles.

The second case mentioned above often exists, for example, occasionally catching up with a bidding document, for example, the customer suddenly experienced a BUG and was eager to modify it.

In the third case, it is quite confusing. For example, if you don't know where to come up with a meeting, open to a workshop;

The fourth case is quite special and common. people sit in the same room and have their own hearts. A common farming scene, but the fruit does not see two beans. This is a time for everyone to spend all their time together. Can programmers improve themselves with this time? Of course you can't. On the surface, you still have to work.

In the fifth case, we won't talk about it because it is the root.

In short, the software company is "busy", generally the above three "busy", and occasionally none of these three, the fourth will come out immediately. The impact of this situation on programmers: chaos and disorder, resentment by heart, hypocrisy, less learning time.

Impact of nonstandard software company processes on programmers:There are no decent demands, no decent design, no tests, no documents, and no maintenance (the so-called maintenance is also a major change for customers to test bugs ). In fact, the demand is not completely a problem for software companies. In most cases, the customers gradually understand what their needs are after coding them.

The problem with "nothing" is that there is nothing clear. If you write a bunch of code that should remain unchanged, first, time is not allowed, and second, it is too difficult. If you are confused about implementation, expansion and maintenance are poor, and the whole pile of bean curd residue projects cannot be started in short. With a bunch of "iron" skills, the gods are not like God, the programmers are not like programmers.

The impact of this situation on programmers: no planning, low code quality, busy schedule, and technology will always stay at the "hitting" level.

The impact of software companies' "full coverage" requirements on programs:Installing the system, repairing the printer, writing documents, coding, seeing customers, sweeping the floor and moving the table, and connecting the network cable are all possible for programmers in domestic software companies to do anything. In terms of technology, everything is required to be done. You can check the recruitment requirements.

This situation has an impact on programmers: There is no specialization in the industry.

The impact of wage arrearage on programmers in software companies:Sadly, this exists. I have always thought that the bottom line for an employee to work with the company should be pay-as-you-go. But many companies have broken this bottom line. A friend joked: "Who is a programmer if the family has money !" Although this is only half the credibility, the quality of life for programmers is still not high from the domestic situation. wage arrears directly affect the mentality of programmers and even affect the lives of programmers.

This situation has an impact on programmers: low-key, confused, unstable mentality, indecisive thinking, and difficult life.

Impact of software company requirements on software development on programmers:Software companies generally require implementation for software development. If we write a program like Notepad, the company feels that programmers should do it within one day; if we write a WPS, the company feels that programmers should do it within two to three months. This is not an exaggeration. It is true. The company's focus is on "just a little functionality", rather than "how to implement this" feature.

The impact of this situation on programmers: difficult development, difficult maintenance, high pressure, and difficult communication.

Impact of a software company's commitment on programmers:Domestic software companies generally have poor actual mobility capabilities, but they do not have the ability to speak. They also know that they are not rational, so they prefer to promise that the actual problems will be solved in the future. However, the promise is just verbal, with the meaning of "I am guaranteed by personality. But in general, programmers in China are still more patient (from the above point of view, can we still mix up), but the company-level "personality" is not credible, more promises and less fulfillment, employees have heard a lot of things that have not been done after two years. However, Lu Yao's horse is weak, and people change their minds for a long time. The result is that the company and its employees often go into a vicious circle.

The impact of this situation on programmers: dissatisfaction, passive, unable to afford to put down, dilemma.

Conclusion

Negative, weak, unassertive, hypocritical, unpromising, unordered, resentful, hypocritical, less learning time, no planning, low code quality, busy, and technology will always stay in level of "Hitting the iron", no specialization in the industry, low-key, confused, instable mentality, wandering thoughts, difficult life, difficult development, difficult maintenance, great pressure, hard communication, dissatisfaction, passive, unable to cope with the dilemma. The above phrases summarize the character, mentality, living environment, and working environment of programmers. They are just like toxins, and can destroy a healthy programmer for a long time. In this environment, why is your technology so low? That's funny.