Skip to content

Instantly share code, notes, and snippets.

@gigamonkey
Last active August 29, 2015 14:22
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gigamonkey/03efdb275e487da37c59 to your computer and use it in GitHub Desktop.
Save gigamonkey/03efdb275e487da37c59 to your computer and use it in GitHub Desktop.
How to collaborate on technical problems

“[A] good problem description had to satisfy everyone. If two people saw a problem from a different point of view, both people’s points of view were merged into the problem description, making the problem more complicated, and making solutions sometimes harder to achieve. But this was essential to addressing porting problems, for example. One couldn’t just solve how a file system operation would work on one operating system unless the solution was going to work on other operating systems, too. On the other hand, the “proposal” field was very different. If two people disagreed on a proposal, they each wrote their own proposal so that proposals could be internally consistent and coherent. This meant that a single problem often had several proposed solutions with different costs and benefits, and the committee had to decide which was the stronger proposal.”

From http://www.nhplace.com/kent/Papers/cl-untold-story.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment