Like most things in life, I'd say the real answer is purely relative.
I believe the most important thing to know isn't if it's bad or good, its can it be made better?
The reason why there is no set rule for "perfect code", or "bad code" is its all relative. There are some red flags, and code smells, but I'm sure there are cases where these rules are to be broken. 😉
I believe all code could be improved. To believe all code is bad is a way you can go about improving yourself and code, rather than considering things black and white.
But this means that you can't just throw around this phrase without specifying what exactly you want to say. There is no single definition of bad code everybody agrees on...
I agree that it's mostly relative and purpose-determined, though everyone develops some personal aesthetic sense over time.
Gerald Weinberg writes in his timeless piece The Psychology of Computer Programming that an objective question to ask is if the code lives up to the requirements.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Like most things in life, I'd say the real answer is purely relative.
I believe the most important thing to know isn't if it's bad or good, its can it be made better?
The reason why there is no set rule for "perfect code", or "bad code" is its all relative. There are some red flags, and code smells, but I'm sure there are cases where these rules are to be broken. 😉
I believe all code could be improved. To believe all code is bad is a way you can go about improving yourself and code, rather than considering things black and white.
👍
But this means that you can't just throw around this phrase without specifying what exactly you want to say. There is no single definition of bad code everybody agrees on...
The best code is no code.
About your last link, this issue made me lmfao: github.com/kelseyhightower/nocode/.... Plenty more like this one in the issues!
I agree that it's mostly relative and purpose-determined, though everyone develops some personal aesthetic sense over time.
Gerald Weinberg writes in his timeless piece
The Psychology of Computer Programmingthat an objective question to ask is if the code lives up to the requirements.