I've been thinking in a similar direction about too-narrow definitions of "good code". I've found it good to distinguish between goals of efficiency, readability, flexibility, and brevity.
Thanks for sharing the post. I really like these four distinctions. Any model that helps us think/reason/communicate more clearly about the more non-trivial aspects of our code is a win for teams.
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.
I've been thinking in a similar direction about too-narrow definitions of "good code". I've found it good to distinguish between goals of efficiency, readability, flexibility, and brevity.
A few weeks ago wrote this post elaborating:
dev.to/wanderingstan/good-code-bal...
Thanks for sharing the post. I really like these four distinctions. Any model that helps us think/reason/communicate more clearly about the more non-trivial aspects of our code is a win for teams.