This /sounds/ like a good idea until the reality of trying to get someone random to fix an actual hardware problem over the phone sets in.
It only takes one idiot pulling the wrong drive once.
(to be clear, spend the money on oob management, too. Serial consoles are essential if you want to have a hope of knowing why that server rebooted last night. And you need to be able to monitor your power draw; it really doesn't cost that much more to spring for the PDU that can monitor and switch the outlets.)
The problem is power is even more expensive there than in SF.
Edit: "for" -> "from"
Never mind. Who cares.
https://news.ycombinator.com/item?id=2984932
Basically, he was too mean in a comment thread. The submissions on HN typically run media hot (X is doomed, Y is for idiots, Z is braindead) while the comments run media cold. He got the two mixed up, and was banned.
I'm hoping the Hurricane Electric facility he mentions is Fremont 2. The Fremont 1 facility has been plagued with power and packet loss issues over the last year (ask your friends with Linodes in Fremont all about it ;)
It also seems a shame to put both of the deployments so close together. Proximity to your machines is a non-issue with a decent colo provider: his example of driving to Vegas every time a drive fails assumes that the provider would be unable or unwilling to sell him 20 minutes of remote hands. Spend a little extra money up front for out-of-band access to your infrastructure and leverage the provider for the physical stuff!