What are developers called who write low-quality code, but make products?

Question

IT terminology

There is a type of programmers who know a lot, can do a lot, but they don't do it well, everything is on crutches, but the product is ready and working.
What are these programmers called?
For example, there is a programmer who writes in php / js, but he only heard about algorithms, design patterns (did not read, did not apply), does not write or write tests, does not follow PSR, etc., etc.
At work, he develops on laravel and bitrix, but the code there is like this:

// какой-нибудь метод
if($type == "Магазин"){
#простыня кода на строчек 60 с вложенными проверками, уровень которых бывает доходит до 5-6
}

But he has been doing this for 10 years already, he is quite experienced and knows the problem areas, what can go wrong, in general, in an emergency, he will be able to insert a crutch and fix it, or make some kind of product, they often hold the position of senior
Tell me, is this generally a normal practice?
A couple of months ago I got a job, and there is such a picture, I try to do it qualitatively, remove crutches, etc., but it seems to me that they are not particularly happy with me, because I spend more time on tasks, while adult uncles write and write products, no matter how, the main thing is that it works!

Answer 1

Geniuses.
Seriously. After all, to make a working spaghetti code without bugs, you need to have almost perfect logical, critical and abstract thinking and a huge supply of RAM (in your head, not on your computer).
Such people should learn to write correctly a little, and they will be invaluable.

Answer 2

You can be a smart person
And think about the beauty of your nails:
Why argue fruitlessly with the age?
Custom despot among people.
The bottom line is that you should also be focused on the release of the product, but at the same time make sure that your code does not completely slide into shit. Both extremes are bad, you need to be able to stay in the middle.

Answer 3

Bydlokoder. Hinducoder. For examples - govnokod.ru The main
problem with poorly written code is that it exponentially increases the cost of further development and troubleshooting.
At some point, the development literally "gets up" - new features stop being released, and the developers refactor the whole collective farm for 6-8 months (management runs and yells at the same time. However, they always run and yell).
Even skilled developers churn out garbage when they solve a problem that is new to them or use tools that are new to them. For good developers, at the same time, the backlog and FPV grow, for bad developers, only FSF.
Good code should be rewritten at least twice before entering the market, going through experimental -> staging -> release, and not just that.
The shitty code is obtained from working in the expelsease mode (figak-figak - and in production).

Answer 4

As a rule, a developer does not have an idea to write shit code, so he writes it when:
Of all this, only the first point is critical. In all the rest, either it is not necessary, or a management error.

Answer 5

There are many places like this: do it quickly and make it work.
If it flies, we'll refactor it later.
But then it rarely happens...

Answer 6

does not write or write tests, does not follow PSR

such people are called govnokoderami. They try not to work with them

Answer 7

while adult uncles write and write products, no matter how, the main thing is that it works!

A well-posed question is half the answer.
To make the current situation adequate, it would be worth asking the same question to those who use all these products for their intended purpose, that is, businessmen.
K.m.k. the answers would amaze you ...
Therefore, alas and ah, but your question, asked on this resource, is doomed to endless generation of useless disputes and reasoning, nothing more, and its usefulness catastrophically tends to zero

Answer 8

It's called bidlo-develop

Answer 9

What idealists are all))
In my personal practice, there are both projects on which I painstakingly sit licking the framework, and there are those where they were told to do it quickly. And I don't care what anyone thinks about the quality of the code. What is paid for is done. Moreover, if I was asked to support my project, about which at the beginning it was just like “fuck it up”, I would either refuse or explain that it would cost much more in terms of man-hour. Fortunately, there are only a couple of such projects and they have gone to work for beginners. There is nothing for them to learn from it.
With age, of course, I became less categorical, I argue with the customer, and sometimes, at the expense of my personal time, I do not do as poorly as the managers want. Subsequently, it pays off when the need arises for a redesign, which, with a properly built architecture, takes 2 times less time than I knock out money for it. In general, anything can happen and sometimes you really need to be able to cheat if the situation requires it. But if bydlokoding has turned into your job - do not be too lazy to start a personal project in which you will realize all your wet dreams and best practices so that your skills do not slide down to the level of your product.
If anything, we are talking about mobile development.