Critical Thinking
Argumentation: Logic vs Rhetoric
Why do smart people make bad technical decisions? Usually because rhetoric defeats logic. The ability to separate 'this sounds convincing' from 'this is logically sound' is one of the most valuable skills a senior engineer can have.
- In code review, architecture meetings, sprint retros, and negotiations with product over technical priorities - whoever builds the stronger argument wins.
- Not whoever has been there the longest or speaks the loudest.
Предварительные знания
Logic vs Rhetoric: Two Paths to Persuasion
A **logical argument** persuades because it is true: if the premises are correct, the conclusion follows inevitably. A **rhetorical argument** persuades because it is emotionally or socially appealing, regardless of its truth. Both are legitimate, but they're used in different contexts.
**Manipulation vs persuasion:** rhetoric becomes manipulation when it conceals logical weaknesses or substitutes emotion for evidence. The test: remove the emotional language from the argument. If it's still convincing - it's honest rhetoric. If it falls apart - the argument was hollow to begin with.
A colleague says: 'All successful companies use microservices, so we need to switch to them too.' What type of argument is this?
Argument Structure: Toulmin and AREA
**The Toulmin Model** breaks an argument into components: Claim, Data, Warrant (the connecting principle), Backing (support for the warrant), Qualifier (limiting conditions), Rebuttal (counterarguments). Using all 6 components means building a professional-grade argument.
**Practical technique:** before an important presentation or email, explicitly write out all 6 Toulmin components. The strongest objections come from weak warrants (why do the data support the claim?) and missing qualifiers (when does the argument break down?).
In the Toulmin model, the 'warrant' is:
Logical Fallacies in Technical Discussions
Logical fallacies are errors in reasoning that make an argument invalid. In technical discussions they appear more often than one might expect. Being able to recognize and name them is a powerful tool.
**Naming fallacies is a dangerous weapon!** Saying 'that's a false dichotomy' can shut down a discussion, but it can also come across as condescending. It's usually better to ask: 'Are there intermediate options between X and Y?' This achieves the same goal with less risk of conflict.
'Agile works at Google and Facebook, so we need to implement Agile too.' What fallacy is this?
Key Ideas
- Logos, ethos, pathos - three modes of persuasion; a strong argument combines all three
- Rhetoric ≠ manipulation as long as it doesn't conceal logical weaknesses
- Toulmin model: claim + data + warrant + backing + qualifier + rebuttal
- Warrant is the most vulnerable part; smart opponents attack it first
- Top tech fallacies: false dichotomy, appeal to authority, slippery slope
- Instead of naming fallacies - ask clarifying questions
What's Next
Strong argumentation rests on mental models. Understanding First Principles, Inversion, and Second-Order Thinking enables building arguments resilient to any counterattack.
- Mental Models for Engineers — Mental models are the 'warrant' of any argument: the principles it rests on
- Analyzing Real Technical Decisions — Real case studies - practice building arguments in context
Вопросы для размышления
- Take the last technical decision that sparked disagreement. What argument was used - logical or rhetorical?
- Break down the argument 'we need to rewrite this module' using the Toulmin model. Which part is the weakest link?
- How might understanding logical fallacies change the culture of code review in a team?