Here's how you can steer clear of common logical fallacies in programming.

As a programmer, you're constantly solving puzzles, but sometimes logical fallacies can trip you up. These mental missteps can lead you down the wrong path, causing you to spend hours on a problem that has a simple solution. Understanding and avoiding these fallacies can save you time and frustration, and improve your programming skills. Whether you're a beginner or an experienced coder, being aware of these common pitfalls is crucial for writing efficient and error-free code.

1 Avoid Hasty Generalizations

When you're debugging or trying to improve your code, it's easy to make hasty generalizations based on limited information. For example, if a function fails once, you might assume it's faulty without considering other factors that could have caused the error. To avoid this, thoroughly test your code under various conditions. Use unit tests, which are scripts written to check individual pieces of code, to ensure that your functions work as intended in different scenarios.

Add your perspective

Nicola Pace

R&D Software Engineer @ E80 Group
Report contribution
I agree a lot with the fact that unit tests are really important. They let you check the correct implementation of individual pieces of code and you are sure that each function does what it is meant to do.

Like

2 Question Confirmation Bias

Confirmation bias is the tendency to search for, interpret, and remember information that confirms preexisting beliefs. In programming, this might lead you to overlook errors or alternative solutions because they don't align with your initial hypothesis. To counteract this, actively seek out information that challenges your assumptions. Code reviews, where another programmer examines your code, can provide fresh perspectives and reveal overlooked mistakes.

Add your perspective

Nicola Pace

R&D Software Engineer @ E80 Group
Report contribution
Also pair programming can be a winner here, writing code and discussing it with another member on the team can be really helpful and also probably better than asynchronous code reviews.

Like

3 Beware of False Dichotomies

A false dichotomy occurs when you consider only two possibilities when there are in fact more options available. In programming, this might manifest as thinking you must choose between two algorithms, when a hybrid or entirely different approach could be more effective. Always explore a range of solutions and consider their trade-offs. This can be done by researching algorithms and design patterns that address similar problems.

Add your perspective

Nicola Pace

R&D Software Engineer @ E80 Group
Report contribution
Engineers and coders should always try new ideas, research algorithms and design patterns, and try to approach problems in a different way! The Internet and your colleagues can help you a lot in this!

Like

4 Understand Logical Dependencies

Logical dependencies can be tricky; they refer to the sequence in which operations must occur. Misunderstanding these sequences can lead to fallacies of causation, where you might believe one function's output is dependent on another when it's not. To navigate this, map out your code's flow and ensure that each function has a clear input and output. This will help you understand the true dependencies within your code.

Add your perspective

5 Challenge Appeal to Authority

The appeal to authority fallacy happens when you accept a solution or practice just because an expert or experienced developer recommends it. While it's important to learn from others, remember to critically evaluate every piece of advice. Test out these recommendations in your own code to see if they truly offer the best solution for your specific context.

Add your perspective

6 Recognize Survivorship Bias

Survivorship bias is the logical error of concentrating on the people or things that made it past some selection process and overlooking those that did not. In programming, this might mean adopting practices from successful projects without considering the failures. To avoid this bias, examine a range of projects, successful or not, and learn from both their successes and their mistakes.

Add your perspective

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

Add your perspective

Here's how you can steer clear of common logical fallacies in programming.

1

2

3

4

5

6

7

1 Avoid Hasty Generalizations

2 Question Confirmation Bias

3 Beware of False Dichotomies

4 Understand Logical Dependencies

5 Challenge Appeal to Authority

6 Recognize Survivorship Bias

7 Here’s what else to consider

Programming

Rate this article

Thanks for your feedback

More articles on Programming

More relevant reading

Here's how you can steer clear of common logical fallacies in programming.

1

2

3

4

5

6

7

1 Avoid Hasty Generalizations

2 Question Confirmation Bias

3 Beware of False Dichotomies

4 Understand Logical Dependencies

5 Challenge Appeal to Authority

6 Recognize Survivorship Bias

7 Here’s what else to consider

Programming

Rate this article

Thanks for your feedback

Explore Other Skills