anchor.diff:  
   When creating a release, use Git for your source code.
   Since Git is not well-suited to dealing with large binaries,
  -blobs should not be checked into Git.
  +it's a good idea to avoid checking blobs into Git.
   
   Instead:
   
  
positive.code: Beside the workflow, this tutorial explains principles to
  keep in mind when creating BOSH releases:
  
  * BOSH releases do not necessarily depend on the internet.
  * BOSH releases remain buildable for a long time.
  * BOSH releases package up all dependencies.
  * BOSH releases do not add blobs to GitHub.
  * Using underscores in filenames is the BOSH way.
  * Commenting your code to facilitate debugging is the BOSH way.
  
  
negative.code: * **jobs** describe pieces of a service.
  * **packages** provide source code and dependencies to jobs.
  * **src** provides non-binary files to packages.
  * **blobs** provides binaries not checked into a Git repository.
  
  Creating a release entails several judgment calls: what to include, how to structure it, and how to split up jobs and packages.
  
  This tutorial walks you through creating a dev release and then a final release
  that contains a single job, namely a Sinatra app called `ardo`.
  