Where are the lines between bydlokod, intermediate stage and professional programming?

Question

Programming

In maintainability? In performance? In flexibility and independence thanks to the provided modularity? In "just made and works until the end of the century" without bugs?
How do you see a professional and shitcoder? I would like detailed answers, especially with pseudocode or real examples. Site govnokod.ru saw

Answer 1

I'll give you a clear definition of shit code. If you want to.
Shit code is an invention of poor implementation where there are good well-known examples. Using native code instead of the standard library. Reinvention of bubble sort. Own interpretation of "what is MVC". NIH syndrome and lack of basic knowledge.

Answer 2

You see, govokod is something collective. As well as beautiful code.
Nevertheless, we write projects in the first place in order to earn money. Over time, the cost of maintaining code increases. And the task of a good programmer is to reduce the cost of this support as much as possible. That is, in fact, save money for the customer, and earn more for it yourself.
And there are a bunch of books about how to write beautiful code and not write shitty code. Such as pure code, perfect code, gang of four, etc. So - these are all books, first of all, about how to save money (and time, which is generally the same).
If you write the code as in Vasily 's answerfor example, then many will probably call it shit code. But if this is the fastest way for you to complete the task (although there may be ready-made solutions, and you just invented the wheel) and this code is unlikely to change in the future, then what's the difference? Well, except for the lack of spiritual satisfaction.
Therefore, I try to avoid the words "shit code" and "beautiful code". There is code that has good or bad characteristics, in the context of the task being performed. There are many characteristics, from functional ones:
Fulfillment of the task.
No bugs.
Work speed.
Qualitative:
Cyclomatic complexity, Connectivity, Focus, Testability, Readability, Comprehensibility, etc.
The recipe for good code is simple. Think about what characteristics are important to you, and whether your code meets these characteristics. If it does not answer, then perhaps this is what is usually called shit code.