Ask HN: Are there any ways to avoid conditional logic?
6 comments
Write it in Prolog, then you won't have to worry about conditionals.
To some extent you can replace conditional logic with polymorphism in languages that support it (Java does).
See, for example:
https://refactoring.guru/replace-conditional-with-polymorphi...
Note that this can be made to work for simple conditionals. It's probably not going to help if you have really complicated conditions, the kind where you need to break out your old discrete math book and draw a truth table and use DeMorgan's Law and all of those other "rules of inference" to work out what happens.
Note also that there are (practical) limits to this in general. Creating lots of classes and overridden methods just to get rid of some conditional logic has the potential to make things even more byzantine and confusing, not less. But done well, and in limited doses, it can be a viable strategy.
See, for example:
https://refactoring.guru/replace-conditional-with-polymorphi...
Note that this can be made to work for simple conditionals. It's probably not going to help if you have really complicated conditions, the kind where you need to break out your old discrete math book and draw a truth table and use DeMorgan's Law and all of those other "rules of inference" to work out what happens.
Note also that there are (practical) limits to this in general. Creating lots of classes and overridden methods just to get rid of some conditional logic has the potential to make things even more byzantine and confusing, not less. But done well, and in limited doses, it can be a viable strategy.
I think the biggest thing is composition over inheritance, and try to put your state into a container like CDI (Using Scoped beans).
If those design paradigms don't work, we've actually had a bit of luck using BPMN and executing it via Drools. This is not "easy" per say but our processes and decision tree were not simple either.
Wishing there was a simpler and modern BPMN like language that supported CDI directly.
If those design paradigms don't work, we've actually had a bit of luck using BPMN and executing it via Drools. This is not "easy" per say but our processes and decision tree were not simple either.
Wishing there was a simpler and modern BPMN like language that supported CDI directly.
In some database apps I can replace all conditionals with loops over sets. If the set is empty nothing happens. The same can be done in other situations which i prefer because it's really robust but it requires such a change in thinking that I don't require it of my team and have not thought about it in a long time.
What does your code look like? Is it like
Feel free to fudge variable names, function names, etc.
if case=1 then (...)
if case=2 then (...)
Feel free to fudge variable names, function names, etc.
Is the problem conditional logic or pretzel logic?
got me thinking, is there a design paradigm that will avoid conditionals all together and yet achieve the same thing? Using java and SQL if it makes any difference.