What is the root cause of shitcode?

Question

Programming

What do you think is the main reason for shitty code in commercial projects?

Question with an asterisk

What is govnokod?

Answer 1

Here's how to see. There can be a lot of direct reasons that lead to shit code:
1. Lack of intelligible analytics and architecture
2. Low qualification of performers (he can and would like to do well, but he doesn’t know and doesn’t know how)
3. Shit coders by nature (there are such people who, even if you create all the conditions, will still do it ****, because it will do)
4. Misunderstanding and difficult relationships in the team
5. Deadlines (some are obviously unrealistic, but some are screwed up in the process)
6. Changing requirements
7. Poorly structured processes (documentation, tests, etc.)
8. Personnel turnover
9. Management policy Etc.
, etc... Many more points can be thought of.
But in the end, all these causes can be reduced to one root cause - poor management. Good management is such an incomprehensible animal... It is difficult to formulate, understand, organize. Weeds are not immediately visible and palpable, but then they turn into problems. If you have a good project manager, he is worth his weight in gold.

Answer 2

Shit code is code that is written based on momentary criteria or criteria that are based on some task that contradicts the main task of the project. Let's say if a programmer gets paid for the amount of code and not for its quality, he will write shitty code. Or if it is most important for him to be in time (to spend a minimum of time), and not to observe the quality of the product. This is under an important condition if the programmer is generally able to write high-quality code in a reasonable time. If not, then any code that he writes automatically obeys only one requirement - imitation of activity, therefore it will be shit code completely or to a large extent.

Answer 3

Robert Martin, in his textbook three volumes - "Clean Code", "Clean Architecture" and "The Ideal Programmer" - writes that the cause of bad code is always the unprofessionalism of the programmer who wrote it, without exception.

Answer 4

Economic feasibility and competence of team leads.

Answer 5

the code doesn't write itself, it's written by people -> that is, the developers themselves are the only reason for having shit code.
It’s another matter that “shit code” is really economically feasible, especially in the context of developing a product with a very short life cycle (for example, prototyping or creating experimental products), and yes, the customer and the manager often push people to this development style.