What are the low skills of Chinese programmers?

First of all, a senior programmer is not relying on their own reading a few tens of thousands of lines of code to be able to build, and I pay more attention to the low-level environment, that is, the programmer's real working environment. Because the programmer's height is actually measured by the actual work, not the other. So I think that the nature of China's software companies can directly lead to the level of programmers. And the software company I'm talking about, doesn't mean one or a few, but the mainstream software companies, the popular software companies. So I hope that the programmers who have entered an ideal company can understand the positioning of my article.

The impact of software companies ' unpaid overtime on programmers:

In the domestic software companies, programmers are often overtime, daily plus, even weeks are often added. And based on this nature, there is a strange phenomenon: every day the programmer's actual work time is always more late than the rules, as to whether one hours later or two hours or more this will have to say, in short, the programmer of this job, if someone on time to work on the back feel like a thief. On the surface, the company doesn't seem to force anyone to work overtime, but there is a subtle deterrent that requires you to work more for the company for a few hours, and on the surface, the hours you're working on are voluntary. And just because you are "willing", the company has more reason to you overtime is considered free.

There is a week does not work overtime, General week does not work overtime because of "busy" (about this quoted "busy", see "software company's ' busy ' influence on programmers"). But weeks of overtime is generally unpaid, as the law stipulates the kind of "compensation" will not taste. But the general company is this stipulation: The week does not work overtime can time-off. About Time-off, general is weeks of class really added, Time-off is not long, the reason is very simple, the company "Busy" well!

The impact of this situation on programmers: negativity, weakness, no ideas, hypocrisy, the future is slim.

The impact of software company's "Busy" on programmers:

The software company's "busy" is sometimes really busy, from the reason that software companies think that the programmer (in fact there are other employees, but this article does not involve discussion) caused by the programmer that the company caused. According to the principle of "one slap and no sound", it should be caused by the vicious circle of cooperation between the company and the programmer. The deep reason everybody studies by oneself. However, from the perspective of my appearance, this kind of "busy" there are a few points, if these points do not represent the views of members, we can add:

* * Project development is out of line with the plan, showing that project development is slower than planning.

* * Sudden events.

* * For some unknown reason, such as show.

* * Fake busy.

* * really busy.

The first situation mentioned above is the most common, which involves the topic of software engineering, but it is also the core of not doing very well, the programmer level is not high. and "software company does not do" has predecessors article "shallow Talk: Why can't the domestic software company bigger do strong?" said, and "the level of programmer is not high" this article said that is, so this reason everyone read these two pieces of their own experience it.

The second situation mentioned above often, such as the occasional bid to catch a tender, such as customers there suddenly appeared a bug, anxious to change and so on.

The third situation is very let a person dizzy dish, a bit of feeling like a moan, such as do not know from where a meeting, open to a seven or eight point;

The fourth kind of situation is very special, also more common, everybody sits in the room, each other's heart. A beautiful sight of common farming, but not two peas in the fruit. It's a waste of time. Can programmers take this time to improve themselves? Of course not, you still have to work on the surface.

The fifth kind of situation does not say, because this is the positive root.

In short, the software company is "busy", generally more than three kinds of "busy", and occasionally these three species are not, the fourth kind will come out immediately.

The impact of this situation on programmers: disorder, resentment from the heart, hypocrisy, and learning time.

The impact of nonstandard software company processes on programmers:

No decent requirements, no decent design, no testing, no documentation, no maintenance (the so-called maintenance is also mostly customers to test bugs to change).

In fact, when it comes to demand this piece is not entirely a software company problem, in most cases, the customer is based on the programmer directly to the code exposed after the problem is gradually understand what their needs are.

The problem with "nothing" is that nothing is clear, and if you write a bunch of quo code, first, time does not allow, second, too much difficulty. If the muddle to achieve, expansion and maintenance of poor, the whole pile of tofu slag project, in short, can not do. A heap of "iron" skills, God does not like God, programmers are not like programmers.

The impact of this situation on programmers: no planning, low code quality, scrambling, technology always stay in the "iron" level.

The impact of software companies ' versatile ' requirements on programmers ' employees on programs:

Install systems, repair printers, write documents, code, see customers, sweep the table, connect the network cable, in the domestic software companies, programmers do anything possible. Just say the technical aspect, is also requests everything to be able to do, looks at the recruitment request to know.

The effect on programmers: no specialization in the surgery industry

The impact of a software company's payroll default on programmers:

Sadly, it exists. I always think that the bottom line for an employee to work with the company is to pay the amount on time. But many companies have broken the line. A friend jokingly said: "Family money, who do programmers Ah!" This is only half credible, but from the domestic situation, the quality of life of programmers is still not high, the arrears of wages directly affect the mentality of programmers, and even affect the life of programmers.

This situation affects programmers: low-key, confused, unstable mentality, wandering thoughts, life difficulties.

The impact of software companies ' requirements on software development on programmers:

Software companies ' requirements for software development are generally realized. If you write a program like Notepad, the company feels that the programmer should fix it in a day; If you write a WPS, the company will feel that the programmer should be in months. It's not pompous, it's the truth. The point that the company is looking at is "just a little bit of functionality," rather than "how to achieve this" function.

The impact of this situation on programmers: development is difficult, maintenance difficult, pressure, difficult to communicate.

The impact of software company commitments on programmers:

Domestic software companies generally do not have the ability to act, but not difficult to speak, they also know that they do not, so love commitment, the actual problem thrown to the future to solve. However, the commitment is only verbal, there is a little "I guarantee the personality" meaning. However, in general, domestic programmers are more tolerant (from the above to see if the patience can be mixed), but the company level of "personality" is not credible, more promises less cash, the staff interviewed to hear the speech to dry for two years did not do is not uncommon. However, the road remote horse weakness, the day long people change their heart, such results are often the company and employees into a vicious circle.

The impact of this situation on programmers: dissatisfaction, passivity, can't afford to put up, dilemma.

Conclusion：

Negative, weak and independent, hypocritical, uncertain about the future, chaos and disorder, resentment by the heart, hypocrisy, learning time, no planning, low code quality, scrambling, technology forever stay in the "iron" level, no specialization in the art, low-key, confused, unstable mentality, wandering thoughts, life difficulties, development difficult, difficult to maintain, Pressure, difficult to communicate, dissatisfaction, passive, can not afford to put down, dilemma.

These phrases sum up the programmer's character, mentality, living environment, working environment and so on, they are like toxins, and can destroy a healthy programmer for a long time. In this environment, also asked why your technology is so low? It's hilarious.