this post was submitted on 24 Sep 2024
82 points (92.7% liked)
Programming
17083 readers
918 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
view the rest of the comments
EDIT: read the article turns out it's super useful... It gives insight into decision table which is a pattern I did not know about until recently...
Is this really a recurring design pattern for y'all?
I mean, you can just use a switch. anyways I'll read the article and see ;)
I can't find it right now, but there is some explanation in "Clean Code" why switches shouldn't be used all over the place.
Google for "replace conditional with polymorphism".
Just checked and it is in "Clean Code" - Chaper 17; Section G23 "Prefer Polymorphism to if/else or switch/case".
Thank you!
This is really terrible advice. Sometimes it's better to do that, but definitely not in the example from this article.
If anyone says you should always prefer polymorphism to switches they are a bloody idiot.
I always love watching people falling for Clown-Bob's advises...
Let's go, let's eat shit on toasts! It's just a matter of how thin you can spread it to hide the taste...