You're a computer engineer and you need to avoid logical reasoning biases. How can you do it?

2 Anchoring bias

Anchoring bias is the tendency to rely too much on the first piece of information we receive when making judgments or estimates, and adjust them insufficiently based on new data. This can affect our accuracy, efficiency, and creativity. For example, you may have a preconceived notion of how long a project will take or how much it will cost based on a previous experience or a rough estimate, and stick to it even when new factors or requirements emerge. To avoid anchoring bias, you should avoid making hasty judgments, gather more information, and update your estimates regularly.

3 Framing effect

Framing effect is the tendency to be influenced by the way a problem or a question is presented, rather than by the facts or the logic behind it. This can affect our preferences, choices, and actions. For example, you may be more likely to accept or reject a proposal based on how it is worded or emphasized, rather than on its merits or drawbacks. To avoid framing effect, you should try to restate the problem or the question in different ways, compare the pros and cons objectively, and avoid emotional or persuasive language.

4 Availability heuristic

Availability heuristic is the tendency to judge the likelihood or frequency of an event based on how easily we can recall or imagine examples of it, rather than on statistical evidence or logic. This can affect our risk assessment, planning, and problem-solving. For example, you may overestimate or underestimate the probability of a system failure, a security breach, or a user error based on your recent memory or exposure to similar scenarios, rather than on actual data or analysis. To avoid availability heuristic, you should rely on facts and figures, seek out diverse sources of information, and avoid generalizing from anecdotes or stereotypes.

5 Hindsight bias

Hindsight bias is the tendency to believe, after an outcome is known, that we could have predicted or prevented it beforehand, or that it was inevitable or obvious. This can affect our learning, feedback, and improvement. For example, you may think that you knew all along that a bug would occur or that a feature would be successful, or that you could have done something differently to avoid or enhance the outcome. To avoid hindsight bias, you should document your reasoning and expectations before the outcome, evaluate the results objectively and constructively, and acknowledge the role of uncertainty and chance.

6 Sunk cost fallacy

Sunk cost fallacy is the tendency to continue investing time, money, or effort in a project or a decision that is not yielding the desired results, because of the amount of resources already invested, rather than cutting your losses and moving on. This can affect your productivity, profitability, and innovation. For example, you may stick to a flawed or outdated design, code, or technology, because you have spent too much time or money on it, rather than adopting a better or newer solution. To avoid sunk cost fallacy, you should focus on the future benefits and costs, not the past ones, and be willing to change your course of action when necessary.