Code quality more important than code functionality.

End of discussion

I essentially agree, but its important to remember that good quality code that doesnt quite do the right thing is technical debt.

@CrashOverride Yet, it's still better than dirty functional code which becomes a hell to maintain.

Not from an economical perspective,at least not in practice today. Because bosses (usually) ain't coders, or at least not good one who keep coding and polishing their skills.

this is utter bollocks.

@kunashe Much discussion, such descriptive.... care to elaborate your point?

echo "Hello World!";

Clean, but an useless piece of shit.

I would argue that code quality and code functionality doesn't actually need to be exclusive towards one another, it is simply we're forced to ignore our code quality due to external constraints, or simply poor discipline.

@JKyll you're right if you only consider short term. In the long run, functional but dirty code becomes a burden to maintain and enhance, and ends up costing way more. And, usually, ends up ours. Bosses who want quick and dirty code usually complain about delays and poor quality later on. Not the best people to work for/with. Unless they plan to release new, dirty shitty productd every 6 months without ever maintaining them or reusing their code.