thinking-via-negativalisted

# Via Negativa ## Overview Via Negativa, articulated by Nassim Taleb in "Antifragile," is the principle that improvement often comes from subtraction rather than addition. We're biased toward adding (features, processes, complexity) when removing (bugs, friction, unnecessary work) often provides more value with less risk. **Core Principle:** Focus on what to remove, not what to add. Subtraction is more robust than addition. ## When to Use - System simplification - Process improvement - Feature prioritization (what NOT to build) - Performance optimization - Reducing technical debt - Personal productivity - Decision-making (what to avoid) - Code review (what to delete) Decision flow: ``` Trying to improve something? → First instinct is to add? → yes → PAUSE, CONSIDER SUBTRACTION → Can you achieve the goal by removing instead? → yes → REMOVE FIRST → Is current complexity necessary? → no → SIMPLIFY VIA NEGATIVA ``` ## The Via Negativa Process ### Step 1: Identify What to Eliminate Instead of "What should we add?", ask: ``` - What's not working that we should remove? - What's causing harm we should stop? - What's unnecessary complexity we should eliminate? - What's outdated that we should delete? ``` ### Step 2: Catalog Candidates for Removal List elements that might be subtracted: ```markdown ## Candidates for Removal Code: - Dead code (unreachable) - Deprecated features (still running) - Unused dependencies - Redundant abstractions Process: - Meetings that