Poster
Print on A3, landscape, at 100% scale: every law with the force that stops it.
HammurabiEngineering laws, each with its counter-force.
- § 1Type 1 vs Type 2 DecisionsCounter-force: Hidden One-Way Doors
- § 2Normalization of DevianceCounter-force: Error Budget
- § 3Chesterton's FenceCounter-force: Time-Boxed Archaeology
- § 4Normalcy BiasCounter-force: Alarm Fatigue
- § 5Law of TrivialityCounter-force: Names Are Interfaces
- § 6Gall's LawCounter-force: Some Systems Cannot Grow From a Toy
- § 7Conway's LawCounter-force: Monolith First
- § 8Hyrum's LawCounter-force: Deliberate Variance
- § 9Brooks' LawCounter-force: Partitionable Work
- § 10XY ProblemCounter-force: Answer the Question Asked
- § 11Postel's LawCounter-force: Maintaining Robust Protocols (RFC 9413)
- § 12Hanlon's RazorCounter-force: Assume Breach
- § 13Hofstadter's LawCounter-force: Parkinson's Law
- § 14Goodhart's LawCounter-force: Balanced Scorecards
- § 15Lindy EffectCounter-force: The Substrate Changes
- § 16Sunk Cost FallacyCounter-force: The J-Curve
- § 17Cargo Cult EngineeringCounter-force: Proven Practice
- § 18Amdahl's LawCounter-force: Gustafson's Law
- § 19Law of Leaky AbstractionsCounter-force: Information Hiding
- § 20Pareto PrincipleCounter-force: The Long Tail
- § 21Survivorship BiasCounter-force: Learning From Success (Safety-II)
- § 22Kernighan's LawCounter-force: Leverage of Abstraction
- § 23Cobra EffectCounter-force: Incentives Mostly Work
- § 24Dunbar's NumberCounter-force: Coordination Through Interfaces
- § 25Worse is BetterCounter-force: The Right Thing
- § 26Cunningham's LawCounter-force: Wrong Answers Persist
- § 27Bystander EffectCounter-force: Single Point of Failure
- § 28Murphy's LawCounter-force: Risk Budgeting
- § 29Boy Scout RuleCounter-force: One Reason Per Diff
- § 30Tesler's LawCounter-force: Accidental Complexity
- § 31Dunning-Kruger EffectCounter-force: Calibrated Confidence
- § 32Curse of KnowledgeCounter-force: Write for Your Audience
- § 33Swiss Cheese ModelCounter-force: Normal Accident Theory
- § 34Premature OptimizationCounter-force: Performance Is Architecture
- § 35Linus's LawCounter-force: Many Eyes, Few Looking
- § 36CAP TheoremCounter-force: PACELC / Tunable Consistency
- § 37Little's LawCounter-force: Utilization
- § 38Two Generals ProblemCounter-force: Good-Enough Certainty
- § 39Peter PrincipleCounter-force: People Grow Into Roles
- § 40Parkinson's LawCounter-force: Slack
- § 41Wirth's LawCounter-force: Programmer Time Over Machine Time
- § 42Ninety-Ninety RuleCounter-force: Good Enough to Ship
- § 43Eagleson's LawCounter-force: Comments Rot
- § 44Hick's LawCounter-force: Expert Efficiency
- § 45Fitts's LawCounter-force: Deliberate Friction
- § 46Miller's LawCounter-force: Too Much Chunking
- § 47Fallacies of Distributed ComputingCounter-force: Don't Distribute
- § 48Ironies of AutomationCounter-force: Toil
- § 49Principle of Least PrivilegeCounter-force: Psychological Acceptability
- § 50Kerckhoffs's PrincipleCounter-force: Defense in Depth
- § 51Gustafson's LawCounter-force: Amdahl's Law
- § 52The Tail at ScaleCounter-force: Redundancy Has a Price
- § 53Ashby's Law of Requisite VarietyCounter-force: Constrain the Environment
- § 54Law of DemeterCounter-force: Pragmatism over Dogma
- § 55Jevons ParadoxCounter-force: Cap the Rebound
- § 56Normal Accident TheoryCounter-force: High-Reliability Organizations
- § 57Broken Windows TheoryCounter-force: Repair Is Not Free
- § 58YAGNICounter-force: Chesterton's Fence
- § 59KISS PrincipleCounter-force: Ashby's Law of Requisite Variety
- § 60DRY PrincipleCounter-force: Duplication Is Cheaper Than the Wrong Abstraction
- § 61Theory of ConstraintsCounter-force: The Constraint Moves
- § 62Occam's RazorCounter-force: Hickam's Dictum
- § 63Single Responsibility PrincipleCounter-force: Premature Decomposition
- § 64Principle of Least AstonishmentCounter-force: Astonishment Is Relative
- § 65Second-System EffectCounter-force: Dead-End Architecture
- § 66Moore's LawCounter-force: Wirth's Law
- § 67Amara's LawCounter-force: Some Things Simply Do Not Arrive
- § 68The Bitter LessonCounter-force: Compute Is Not Free
- § 69Metcalfe's LawCounter-force: The Same Quadratic Is a Cost
- § 70Ringelmann EffectCounter-force: Separable Contribution
- § 71Shirky PrincipleCounter-force: Some Problems Are Permanent
- § 72Error BudgetCounter-force: Normalization of Deviance
- § 73ToilCounter-force: Ironies of Automation
- § 74Blameless PostmortemCounter-force: Diffused Ownership
- § 75Working BackwardsCounter-force: Build to Learn
- § 76Disagree and CommitCounter-force: Groupthink
- § 77You Build It, You Run ItCounter-force: Developer Cognitive Load
- § 78Static StabilityCounter-force: Cost of Idle Capacity
- § 79Avoid FallbackCounter-force: Graceful Degradation
- § 80Constant WorkCounter-force: Elasticity
- § 81Mechanisms, Not Good IntentionsCounter-force: Resist Proxies
- § 82Andon (Stop the Line)Counter-force: Throughput Pressure
- § 83Five WhysCounter-force: Swiss Cheese Model
- § 84Chaos EngineeringCounter-force: First, Do No Harm
- § 85Context, Not ControlCounter-force: Guardrails
- § 86Approve What Improves Code HealthCounter-force: Broken Windows Theory
- § 87Beyoncé RuleCounter-force: Churn Rule
- § 88Churn RuleCounter-force: Code Ownership
- § 89Fixed Time, Variable ScopeCounter-force: Quality as the Hidden Variable
- § 90Strangler FigCounter-force: Clean Cutover
- § 91Choose Boring TechnologyCounter-force: Fitness for Purpose
- § 92Technical DebtCounter-force: Premature Repayment
- § 93Lehman's Laws of Software EvolutionCounter-force: Stability Is a Feature
- § 94Bus FactorCounter-force: Depth of Ownership
- § 95Pesticide ParadoxCounter-force: Old Tests Still Guard
- § 96Narratives, Not SlidesCounter-force: Working Software over Comprehensive Documentation
- § 97One-Version RuleCounter-force: Semantic Import Versioning
- § 98Genchi Genbutsu (Go and See)Counter-force: Trust the Aggregate
- § 99Believability-Weighted DecisionsCounter-force: Wisdom of Crowds
- § 100Braintrust (Notes Without Authority)Counter-force: Review as a Gate
- § 101Brandolini's LawCounter-force: Cunningham's Law
- § 102Automation BiasCounter-force: Algorithm Aversion
- § 103Small ChangesCounter-force: Per-Change Overhead
- § 104Programming as Theory BuildingCounter-force: Fake the Rational Design
- § 105Test Oracle ProblemCounter-force: Production as the Oracle
- § 106The Lethal TrifectaCounter-force: Constrain the Flow, Not the Tools
- § 107Cost of DelayCounter-force: Reserved Engineering Time
- § 108The Last Responsible MomentCounter-force: Most Responsible Moment
- § 109Pre-MortemCounter-force: Bias for Action
- § 110Wicked ProblemsCounter-force: Understand the Problem First
- § 111Most Ideas FailCounter-force: Conviction Bets
- § 112Kingman's FormulaCounter-force: Headroom Costs Money
- § 113Maker's Schedule, Manager's ScheduleCounter-force: Stop for the Line
- § 114McNamara FallacyCounter-force: Measure It Anyway
- § 115Twyman's LawCounter-force: Trivial Changes Can Have a Big Impact
- § 116Psychological SafetyCounter-force: Felt Accountability