explaingit

nusr/hacker-laws-zh

12,520Audience · developerComplexity · 1/5Setup · easy

TLDR

A Chinese translation of hacker-laws, a curated reference of famous laws, principles, and patterns from software development like Brooks's Law, the CAP Theorem, and SOLID, each with plain explanations and links to Chinese Wikipedia.

Mindmap

mindmap
  root((hacker-laws-zh))
    Software laws
      Brooks Law
      Hofstadter Law
      Broken Windows
    Computing principles
      Amdahls Law
      CAP Theorem
    Human behavior
      Dunbar Number
      Pareto Principle
      Dunning-Kruger
    Engineering rules
      SOLID
      DRY and KISS
      YAGNI
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

Things people build with this

USE CASE 1

Look up why adding engineers to a late project makes it later before your next team deadline discussion.

USE CASE 2

Reference the CAP Theorem entry when evaluating trade-offs in a distributed database design.

USE CASE 3

Use the SOLID, DRY, and KISS entries as a plain-language checklist during a code review.

Getting it running

Difficulty · easy Time to first run · 5min
No license information is mentioned in the explanation.

In plain English

hacker-laws-zh is a Chinese translation of the hacker-laws project, a curated reference of named laws, theories, principles, and patterns that come up frequently in software development discussions. The original English project was created by dwmkerr, this repository is a community-maintained translation into Simplified Chinese with added links to Chinese Wikipedia pages for each entry. The collection covers a wide range of named concepts. Some describe how software projects behave in practice, such as Brooks'''s Law (adding engineers to a late project makes it later), the Broken Windows Theory (visible disorder invites more disorder, applied to code quality), and Hofstadter'''s Law (tasks always take longer than expected, even when you account for that). Others address computing systems directly, including Amdahl'''s Law (the limits of parallelization) and the CAP Theorem (distributed databases cannot simultaneously guarantee consistency, availability, and partition tolerance). Many entries come from outside computing but apply to it: Dunbar'''s Number (a cognitive limit on social group sizes, relevant to team organization), the Pareto Principle (80% of effects from 20% of causes), Occam'''s Razor (prefer simpler explanations), and the Dunning-Kruger Effect (lower competence correlates with overconfidence). Engineering principles like SOLID, DRY, KISS, and YAGNI also have entries with plain explanations. Each entry includes a brief explanation, a real-world example, and links to both English and Chinese Wikipedia pages for further reading. The repository carries a note that it presents these laws without endorsing any particular one, since their applicability depends on the specific situation. This repository contains no code and is a reading reference only. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Using Brooks's Law and Hofstadter's Law, explain why my software project keeps running late and suggest how to frame this for my manager.
Prompt 2
Apply the Pareto Principle to help me figure out which 20% of bugs in my codebase are responsible for 80% of user complaints.
Prompt 3
Using the SOLID principles from hacker-laws, review my Python class design and point out which principles I'm violating.
Prompt 4
Quiz me on ten laws from hacker-laws, give me the name of the law and ask me to explain it before revealing the answer.
Open on GitHub → Explain another repo

← nusr on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.