This is really harsh and it sounds like he's looking for a scapegoat on why he is behind on client projects, "i delayed 3 client deploys in the past week due to

This is really harsh and it sounds like he's looking for a scapegoat on why he is behind on client projects, "i delayed 3 client deploys in the past week due to Github’s downtime". GitHub is very transparent about their issues and from looking at their blog ( http://github.com/blog/597-a-note-on-the-recent-outages http://github.com/blog/597-a-note-on-the-recent-outages ), "Following three months of near 100% uptime, we’ve just been through three major outages in as many days." The outages weren't "days long" so those delays in deploying a client's project shouldn't have been significant. If the client expected a deployment during a short window it is irresponsible for the development company to keep the code only in a single location. I cover this in a post about availability on my blog ( http://www.bretpiatt.com/blog/2009/10/03/availability-is-a-fundamental-design-concept/ http://www.bretpiatt.com/blog/2009/10/03/availability-is-a-f... ).