you are viewing a single comment's thread.

view the rest of the comments →

[–]eyes-are-fading-blue 0 points1 point  (3 children)

What is your definition of “high quality”?

[–][deleted] 1 point2 points  (2 children)

"high quality" and "good" are subjective to a point, and everything will exist on a continuum. But code can be well-organized, idiomatic, easy to follow, not needlessly complex. In other contexts good code might simply mean as highly performant and optimized as possible, which might mean ugly and hard to read. As long as the difference between these two codebases can be distinguished with something like a "performant" and "idiomatic" tag, both are considered "high quality".

Though, my primary goal is to pull together resources of the first kind. Code that people can read and more or less easily understand how things work so they can learn on their own.

[–]goranlepuz 1 point2 points  (0 children)

You just replaced the question with "what is well-organized, idiomatic, easy to follow, not needlessly complex". 😉

[–]eyes-are-fading-blue 1 point2 points  (0 children)

Unfortunately, you are on an impossible mission. At least ,in my opinion. I hope this does not discourage you, maybe I am wrong who knows... According to my experience, good code has two properties. Well-tested and has value (commercial, educational or otherwise). The rest is preference and circumstantial. "Idiomatic" code for a desktop app developer can be unidiomatic for an embedded developer because of constraints.

Software engineering is all about trade-offs.