bcrisp · April 23, 2015 20:17
diff --git a/gistfile1.txt b/gistfile1.txt
 Collaborative Operations is the next evolutionary step in DevOps movement. While DevOps takes the stance of infrastructure as code, removing silos between development and operations, and releasing early and often.

 Collaborative Ops holds the following views:

 - Your infrastructure is code and can be treated as such. Operational stacks can be versioned in Git, rolled back, fast-forwarded, and programmed against. Collaborative Ops allows the entire stack to be represented as a WSDL-like schema that can be programmed against at compile time rather than run time.

 - Infrastructure is a Read Eval Print Loop of modules that can be loaded and unloaded in real time.

 - Systems are represented categorically, with useful notation borrowed directly from category theory. Isomorphisms serve as interfaces; if my Apache web server has an isomorphism to an nginx config, then I can switch back and forth between them with zero configuration.
	Collaborative Operations is the next evolutionary step in DevOps movement. While DevOps takes the stance of infrastructure as code, removing silos between development and operations, and releasing early and often.

	Collaborative Ops holds the following views:

	- Your infrastructure is code and can be treated as such. Operational stacks can be versioned in Git, rolled back, fast-forwarded, and programmed against. Collaborative Ops allows the entire stack to be represented as a WSDL-like schema that can be programmed against at compile time rather than run time.

	- Infrastructure is a Read Eval Print Loop of modules that can be loaded and unloaded in real time.

	- Systems are represented categorically, with useful notation borrowed directly from category theory. Isomorphisms serve as interfaces; if my Apache web server has an isomorphism to an nginx config, then I can switch back and forth between them with zero configuration.