DEV Community

Discussion on: How would you define high quality code?

Collapse
 
jeikabu profile image
jeikabu • Edited

It's subjective and variable depending on the circumstances:

  • Skill and experience of the author (I tend to gloss over PRs by people that do consistently good work)
  • Difficulty/importance of changes
  • ROI for additional time spent etc.

There's an implicit assumption that you can't spend "forever" on a piece of code; at some point it's got to be "good enough" so you can move on. It's also subject to diminishing returns.