Emotional Decision Making vs Evidence-Based Decision Making

Developers should learn about emotional decision making to recognize and mitigate cognitive biases (e meets developers should learn and use evidence-based decision making to enhance the quality, efficiency, and reliability of their work, such as when choosing between programming languages, frameworks, or architectural patterns based on performance benchmarks, security audits, or user feedback. Here's our take.

Emotional Decision Making

Nice Pick

Developers should learn about emotional decision making to recognize and mitigate cognitive biases (e

Pros

• g
• Related to: cognitive-biases, critical-thinking

Cons

• Specific tradeoffs depend on your use case

Evidence-Based Decision Making

Developers should learn and use Evidence-Based Decision Making to enhance the quality, efficiency, and reliability of their work, such as when choosing between programming languages, frameworks, or architectural patterns based on performance benchmarks, security audits, or user feedback

Pros

• It is particularly valuable in agile environments for sprint planning, bug prioritization, and continuous improvement initiatives, as it reduces guesswork and aligns decisions with measurable goals like faster delivery or higher code quality
• Related to: data-analysis, agile-methodologies

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Emotional Decision Making is a concept while Evidence-Based Decision Making is a methodology. We picked Emotional Decision Making based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Emotional Decision Making wins

Based on overall popularity. Emotional Decision Making is more widely used, but Evidence-Based Decision Making excels in its own space.