Critical Thinking in IT: Why Smart People Make Terrible Decisions

A brilliant engineer can still make terrible decisions. Google+, Theranos, Knight Capital - these failures were not due to a lack of talent. Critical thinking is the skill that separates engineers who build successful systems from those who repeat others' mistakes.

• **Hype-driven development:** Rewriting everything in a new framework every two years
• **Cargo cult:** 'Google does it this way' without understanding their context
• **Sunk cost:** 'We've been building this for 6 months - we can't give up now'
• **Authority bias:** 'The CTO said so - it must be right'

The Smart-Decision Paradox

**The Paradox:** The most talented engineers sometimes make the worst decisions. Companies staffed with the best people still fail spectacularly. Why?

**Key insight:** Technical expertise does not protect against bad decisions. In fact, it often makes things worse - experts overestimate their ability to see the full picture.

The problem is not a lack of knowledge. The problem is **how** we think and make decisions.

What Is Critical Thinking

**Critical thinking** is not about criticizing everything. It is a systematic approach to evaluating information, arguments, and decisions.

**Critical thinking means:** 1. Asking the right questions 2. Examining assumptions 3. Evaluating evidence 4. Considering alternatives 5. Acknowledging uncertainty

Critical thinking is not skepticism for its own sake. It is **reasoned** skepticism aimed at making better decisions.

Why Engineers Need This Most

Engineers are accustomed to working with **deterministic** systems: code either works or it doesn't. But decisions about technology, architecture, and process are **probabilistic** games.

**Common engineering thinking traps:** 1. **Technocentrism**: 'Technology will fix everything' 2. **Over-engineering**: 'Let's get it right from the start' 3. **Hype-driven**: 'New = better' 4. **Authority bias**: 'Google does it this way = correct' 5. **Sunk cost**: 'We've put in so much, we can't quit now'

**Hammer syndrome:** When all one has is a hammer, everything looks like a nail. For engineers, all problems tend to look like technical ones.

First Principles Thinking

**First Principles Thinking** means breaking a problem down to its fundamental truths and building a solution from scratch, rather than copying existing approaches.

**Reasoning by analogy vs. First Principles:** **Analogy:** 'Uber for X' - copying a successful model **First Principles:** 'What fundamental problem are we solving? What are the basic facts?'

**Applying this in IT:**

• 'We need Kubernetes' → 'What problem are we solving? Orchestration? Scaling? What is the minimum viable solution?'
• 'We need microservices' → 'Where are the service boundaries? Why those boundaries? What are the trade-offs?'
• 'GraphQL is more modern than REST' → 'What specific REST problems do we actually have? What cost are we willing to pay?'

Key Takeaways

• **Technical expertise ≠ good decisions.** It can even get in the way.
• **Critical thinking** = asking the right questions + validating assumptions
• **Engineering traps:** technocentrism, hype-driven decisions, authority bias
• **First Principles:** break it down to fundamental truths, then build up
• **Analogy is dangerous:** Netflix ≠ a small startup

What's Next?

This introduction is the foundation. Next come the specific tools:

• Cognitive Biases — Why our brains systematically mislead us
• Evaluating Evidence — How to distinguish facts from opinions
• Trade-off Analysis — How to compare the incomparable

Вопросы для размышления

• Recall a decision that seemed obvious but turned out to be wrong. What assumption was not validated?
• What best practices in a project can nobody explain WHY they exist?
• Where did reasoning by analogy ("X does it this way") happen instead of First Principles?

Связанные уроки

• mm-01-intro