• 41 Posts
  • 193 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle














  • Well it’s in the name, they are code smells, not hard rules.

    Regarding the specific example you cited, I think that with practice it becomes gradually more natural to write reusable functions and methods on the first iteration, removing the need for later DRY-related refactorings.

    PS : I love how your quote for the Rule of Three is getting syntax highlighted xD (You can use markdown quotes by starting quoted lines with > )





  • That’s not what I said. I said that comments can often (but not always) be replaced with good and explicit names.

    This can be pushed to some extreme by making functions that only get called at a single place in the code, just for the sake of being able to give a name to the code that’s inside (instead of inlining it and adding a comment that conveys the same informations as the function’s signature)

    It’s definetly not for everyone, but for beginners/juniors it gives something objective they can aim for when trying to build good coding habits



  • pcouyOPtoProgramming@programming.devCode Smells Catalog
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    1 month ago

    Apart from the fact that, as another commenter said, “smells” are not “rules”, I think most of these points come down to developing good habits, and ultimately save a lot of time in the long run by initially spending some time thinking about maintainability and preventing/limiting technical debt accumulation.