this post was submitted on 01 Sep 2023
329 points (96.1% liked)

Programming

17511 readers
480 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] lysdexic@programming.dev 16 points 1 year ago (2 children)

Duplicate code can be a code smell, but it's far better to have the same function definition or code block appear twice in the code than extracting a function that tightly couples two components that should not be coupled at all.

See Write Everything Twice (WET) principle.

[–] frezik@midwest.social 7 points 1 year ago

Also, some of the deep, highly abstract, functional techniques to reduce duplication are too clever for their own good. Your dev team might worship you as a programming God until someone needs to debug it. Back off on that, even if it means duplicating more code.

[–] SolarMech@slrpnk.net 3 points 1 year ago

This. Especially if your team does not follow SOLID principles (as then someone fixes a bug in a base class method that shouldn't be shared. This fixes an issue in a subclass but introduces one in another. Rinse, repeat.