paulghaddad · December 1, 2014 21:18
diff --git a/gistfile1.txt b/gistfile1.txt
 Explain how "convention over configuration" allows us to be more productive as a group.

 We need to recognize that our needs aren't unique, and must embrace our commonalities as a group. By pushing back against the impulse to create our own solutions to previously solved problems, we allow ourselves to become more productive as a group through shared solutions and tools. A good example of this is the layer of abstractions in our web application stack: assembly-level; C; OSX; POSIX; Ruby; Rack and Rails. By using these shared solutions, we save time by only building what's necessary, and leaving it to the community to build everything else we need. There is no need to recreate the abstraction layer that is OSX to build a web application. Instead, we spend our time experimenting at the top of the stack. 

 Shared solutions give us standards and allows a group to progress by building even more solutions at the top of the stack. At the core, we take shared problems that the community has, and create shared solutions for these problems. This allows us to start on the 400th floor instead of the 1st. It is on the 400th floor that we experiment. And once a great solution arises at the top of the stack, we can declare it a shared solution, where it becomes part of "Convention over Configuration". This cycle thus repeats itself, and we can start each project at a higher level than before, and thus become more productive.
	Explain how "convention over configuration" allows us to be more productive as a group.

	We need to recognize that our needs aren't unique, and must embrace our commonalities as a group. By pushing back against the impulse to create our own solutions to previously solved problems, we allow ourselves to become more productive as a group through shared solutions and tools. A good example of this is the layer of abstractions in our web application stack: assembly-level; C; OSX; POSIX; Ruby; Rack and Rails. By using these shared solutions, we save time by only building what's necessary, and leaving it to the community to build everything else we need. There is no need to recreate the abstraction layer that is OSX to build a web application. Instead, we spend our time experimenting at the top of the stack.

	Shared solutions give us standards and allows a group to progress by building even more solutions at the top of the stack. At the core, we take shared problems that the community has, and create shared solutions for these problems. This allows us to start on the 400th floor instead of the 1st. It is on the 400th floor that we experiment. And once a great solution arises at the top of the stack, we can declare it a shared solution, where it becomes part of "Convention over Configuration". This cycle thus repeats itself, and we can start each project at a higher level than before, and thus become more productive.