explaingit

dwmkerr/hacker-laws

Analysis updated 2026-06-21

27,088HTMLAudience · generalComplexity · 1/5Setup · easy

TLDR

A plain-English reference glossary of laws, principles, and patterns that developers quote in tech discussions, Brooks' Law, Conway's Law, SOLID, DRY, KISS, and dozens more, all explained neutrally in one place.

Mindmap

mindmap
  root((hacker-laws))
    Categories
      Laws
      Principles
    Key entries
      Brooks Law
      Conways Law
      Pareto Principle
      DRY and KISS
    Format
      Markdown reference
      Website
      PDF eBook
    Audience
      Developers
      Tech leads
      PMs
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Look up a tech term like Conway's Law you heard in a code review and get a neutral plain-English explanation with its origin.

USE CASE 2

Browse the full glossary of software engineering cultural vocabulary to understand how developers think and communicate.

USE CASE 3

Share a specific law or principle with your team to ground a design or architecture discussion in shared terminology.

What is it built with?

HTMLMarkdown

How does it compare?

dwmkerr/hacker-lawstencent/weuiaishwaryanr/awesome-generative-ai-guide
Stars27,08827,37026,577
LanguageHTMLHTMLHTML
Setup difficultyeasyeasyeasy
Complexity1/51/51/5
Audiencegeneraldeveloperpm founder

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

In plain English

hacker-laws is a reference collection that gathers, in one place, many of the "laws," theories, principles and patterns that developers and technologists routinely quote in conversation, things like Brooks' Law, Conway's Law, Hyrum's Law, the Pareto Principle, the DRY and KISS principles, SOLID, YAGNI, the Robustness Principle, and so on. It is not a piece of software you run, it is a documentation project, written mostly as a long Markdown file, and it also powers a companion website at hacker-laws.com. The repository works as an explanatory glossary. Each entry names a law or principle, links to a fuller source such as a Wikipedia page, gives a short plain-language description, often includes a quoted definition, and points to related entries. The author is careful to note that the project explains these ideas but does not advocate for any of them, whether a given law should actually guide a decision is a matter of debate and depends on the context. The content is organised into two top-level sections, "Laws" (observations and inevitabilities) and "Principles" (guidelines people consciously try to follow), followed by a reading list, online resources, a PDF eBook download, and a podcast. You would reach for hacker-laws when you hear a term thrown around in a code review, a design discussion or a tech talk and want a quick, neutral explanation of what it actually means and where it came from, or when you want a single place to browse the cultural vocabulary of software engineering. The project is community-maintained, accepts pull requests, and has been translated into more than a dozen languages.

Copy-paste prompts

Prompt 1
Using the hacker-laws definition of Conway's Law, explain how it should influence the way we structure our engineering team when building a microservices app.
Prompt 2
Based on the Pareto Principle as described in hacker-laws, help me identify which 20% of our app features are probably driving 80% of user value so I can prioritize the roadmap.
Prompt 3
Explain Hyrum's Law to a non-technical PM and give a concrete example of how it applies when we're planning to change a public-facing API.
Prompt 4
Help me apply the YAGNI principle to review my project backlog and identify features we should cut because we probably won't need them yet.
Prompt 5
Using hacker-laws definitions, explain the difference between the DRY principle and abstraction, when does following DRY actually hurt a codebase?

Frequently asked questions

What is hacker-laws?

A plain-English reference glossary of laws, principles, and patterns that developers quote in tech discussions, Brooks' Law, Conway's Law, SOLID, DRY, KISS, and dozens more, all explained neutrally in one place.

What language is hacker-laws written in?

Mainly HTML. The stack also includes HTML, Markdown.

How hard is hacker-laws to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is hacker-laws for?

Mainly general.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub dwmkerr on gitmyhub

Verify against the repo before relying on details.