Hammurabi
LawsGitHub日本語

Poster

Print on A3, landscape, at 100% scale: every law with the force that stops it.

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

Text licensed CC BY-SA 4.0. Code licensed MIT. Photos are credited on each article under their own licences. Company logos are trademarks of their owners, shown only to say where a practice comes from.

Card deck / Poster