Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
@BruceAlderman gave a good answer with different aspects that covers the most. I'm not very good at SQL, so my answer is more general. When I have to choose between two different things that are e...
Answer
#2: Post edited
by
klutt
·
2020-11-15T22:38:46Z (over 3 years ago)
- @BruceAlderman gave a good answer with different aspects that covers the most. I'm not very good at SQL, so my answer is more general.
- When I have to choose between two different things that are equivalent in performance and functionality and readability is the only thing that's left. Then I try to describe the result of the operation in plain English (or any other spoken language) and then pick whatever code that most accurately describes the intention of the operation.
I like when programming languages that makes it easier to express your intention. One of my favorites there is the keyword `unless` in Ruby. AFIK it's completely equivalent to `if not`. But in many cases it sounds way more natural. `if not <condition>` tend to give the message "if this condition is not met" in a very dry manner. `unless <condition>` tend to give the message "Always do this. Well, _unless_ this very unlikely event has happened."
- @BruceAlderman gave a good answer with different aspects that covers the most. I'm not very good at SQL, so my answer is more general.
- When I have to choose between two different things that are equivalent in performance and functionality and readability is the only thing that's left. Then I try to describe the result of the operation in plain English (or any other spoken language) and then pick whatever code that most accurately describes the intention of the operation.
- I like when programming languages has features that makes it easier to express your intention. One of my favorites there is the keyword `unless` in Ruby. AFIK it's completely equivalent to `if not`. But in many cases it sounds way more natural. `if not <condition>` tend to give the message "if this condition is not met" in a very dry manner. `unless <condition>` tend to give the message "Always do this. Well, _unless_ this very unlikely event has happened."
#1: Initial revision
by
klutt
·
2020-11-15T16:47:49Z (over 3 years ago)
@BruceAlderman gave a good answer with different aspects that covers the most. I'm not very good at SQL, so my answer is more general. When I have to choose between two different things that are equivalent in performance and functionality and readability is the only thing that's left. Then I try to describe the result of the operation in plain English (or any other spoken language) and then pick whatever code that most accurately describes the intention of the operation. I like when programming languages that makes it easier to express your intention. One of my favorites there is the keyword `unless` in Ruby. AFIK it's completely equivalent to `if not`. But in many cases it sounds way more natural. `if not <condition>` tend to give the message "if this condition is not met" in a very dry manner. `unless <condition>` tend to give the message "Always do this. Well, _unless_ this very unlikely event has happened."