Code Quality Debate

Show me where quality of software is in this discussion.

The discussion here isn't about code. It's about quality of engineers hired. If their software and product quality is steadily declining then that says something about their team. Perhaps they are incredible coders but don't have good business skills or "customer obsession".

This opinion is the reason software quality is shit today.

Part of the answer is in the next sentence:>And because nobody seems to care about these issuesThe word "quality" is very subjective in this case. Perhaps the driver already did everything Qualcomm needed it to do. Maybe the code isn't perfect, but if it's working and money is being made... "if it ain't broke, don't fix it". I'm sure a non-trival amount of people on HN have worked in less-than-good codebases, but finite resources &

I don't think "quality" has anything like a universal definition, and when people say that they probably mean an alignment with personal taste.Does it solve the problem? As long as it isn't prohibitively costly in terms of time or resources, then the rest is really just taste. As a user I have no interest whatsoever if your code is "idiomatic" or "modular" or "functional". In other industries "quality" usually means free of defects,

The first two are product quality, not code quality

Makes you think of how exactly code_quality correlates with commercial success.

It's as if they care more about pretty and shiny than quality code.

Something I learned over the years... if your code quality is too high, it means you're sacrificing productivity.

Just goes to show how much code quality contributes to a successful product.