thinking-steel-manninglisted

# Steel-Manning ## Overview Steel-manning is the opposite of straw-manning. Instead of attacking the weakest version of an opposing argument, you construct and address the strongest possible version. This leads to better decisions, more productive debates, and deeper understanding of trade-offs. **Core Principle:** To truly evaluate an idea, argue against its best form. If you can defeat the strongest version, you've actually learned something. ## When to Use - Design reviews - Evaluating alternative approaches - Conflict resolution - Validating your own decisions - Code review discussions - Architecture debates - When you disagree with someone's proposal - Before rejecting an idea Decision flow: ``` Disagreeing with a proposal? → Can you state their best argument? → no → STEEL-MAN FIRST → Are you attacking a weak version? → yes → CONSTRUCT STRONGER VERSION → Have you found the core insight? → no → DIG DEEPER ``` ## The Steel-Manning Process ### Step 1: Understand the Original Argument Before improving, understand: ```markdown ## Original Proposal Proposal: "We should rewrite the backend in Rust" Stated reasons: - Memory safety - Better performance - Modern language Apparent weaknesses: - Team doesn't know Rust - Rewrite is risky - Current system works ``` ### Step 2: Identify the Core Insight What's the strongest kernel of truth? ```markdown ## Core Insight Behind "rewrite in Rust" is: - Concern about memory-related bugs in production - Performance pr