10 Catch-Rules for DAO Construction

Author: Owocki, DAOSquare

Article 1: Gall's Law

Gale's law states that an efficient complex system always evolves from an efficient simple system. (rather than a complex and unknown system from the beginning). How to use this law: Take advantage of it when designing your minimum viable product.

Article 2: The Pareto Principle (The Pareto Principle)

The Pareto Principle (or 82 Law) states that approximately 80% of effective results come from 20% of key efforts. How to use this law: Take advantage of it when designing your minimum viable product.

Article 3: Parkinson's Law

Parkinson's Law states that work is extended to fill the time or budget to complete the work. How to use this law: Use it to set deadlines that are far enough (but not too far).

Article 4: Goodhart's Law

Goodhart's Law states that when a metric becomes a goal, it is no longer a good metric. How to use this law: Stick to this law when building systems designed to accomplish difficult tasks, such as raising funds for public goods or resisting false identities.

Article 5: Brooks' Law

Fred Brooks pointed out in his book "The Mythical Man-Month" that adding manpower to a delayed software project will make the delay worse. How to use this rule: Keep your team size small.

Article 6: Moore's Law

Moore's Law is an observation made by Intel co-founder Gordon Moore in 1965 that the number of transistors on a chip doubles approximately every two years, but its cost Halved. How to use this law: We are all riding the wave of Moore’s Law organically. This is part of creating huge returns in tech!

Article 7: Metcalfe's Law

Metcalfe's law states that the value of a telecommunications network is proportional to the square of the number of users connected to the system (n^2). How to use this law: Build for exponential value creation!

Article 8: Dunbar's Number

Dunbar’s number suggests that there is a cognitive limit to the number of people with whom one can maintain a stable social relationship. How to use this law: Keep your team size small unless otherwise necessary! If you need to scale your team, be aware of the best trust patterns for each level.

Article 9: The Unix Philosophy (The Unix Philosophy)

The philosophy of Unix is: 1) make each program do one thing well, 2) let the output of each program be the input of another program, 3) write programs to work together. How to use this law: Build modular software!

Article 10: Conway's Law

Conway's Law states that the systems an organization designs will reflect its own communication structure. How to use this law: Design your organization in a way similar to software development. Please note that the overall structure cannot be expanded!