Difference between revisions of "Rough consensus and running code"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
==Additional Resources== | ==Additional Resources== | ||
* [http://www.davidellis.ca/wp-content/uploads/2012/05/Russell-running-code.pdf ‘Rough Consensus and Running Code’ | * [http://www.davidellis.ca/wp-content/uploads/2012/05/Russell-running-code.pdf ‘Rough Consensus and Running Code’ and the Internet-OSI Standards War] (PDF) | ||
and the Internet-OSI Standards War] (PDF) | |||
* [https://medium.com/@shesek/rough-consensus-and-running-code-and-the-internet-osi-standards-war-3eb2fbecc484 An excerpt of the above, on Medium] | * [https://medium.com/@shesek/rough-consensus-and-running-code-and-the-internet-osi-standards-war-3eb2fbecc484 An excerpt of the above, on Medium] | ||
Latest revision as of 14:04, 27 September 2019
Rough consensus and running code means that we should design practical, working systems that can be quickly implemented and solve a problem the a group agrees they have.
For example, If everyone agrees we need images on the web, and someone gets images up and running, whoever gets there first will probably be the one setting the direction for the structure.
The concept was forged during the internet standards wars. “We reject: kings, presidents, and voting. We believe in: rough consensus and running code,” was coined by David Clark in 1992.