The large amount of grammar and spelling errors make me question if the author is at all interested in a "real serious business". And WTF is up with the horrendous comma usage? It's similar on his Nautilus6 and LinkedIn websites, too.
Also, how precisely did temporary downtimes prevent deploys? At best, it appears they would've been delayed by a couple hours, and the great part about Git is that you can work around something like that pretty easily. Granted, downtime is annoying, but his extended difficulties seem to largely stem from his own mistakes, and for $7/month he's not exactly paying top dollar to guarantee uptime.
Like i noted on one of the comments on the post, the need to wait a few hours was due to a last-minute change we had to push.
yes, i do need a better process (even if this case WAS a very specific case that is not likely to happen again) but still, if i pay i want to get the service i pay for.
Github had outages since ever, and although they do seem to do the right thing and make it better, it seems that they are aiming at the wrong direction.
And about the spelling/grammar/whatever errors, i'm just not a native english speaker. Don't think that was the real issue in the post but whatever, one day i'll learn to spell.
The spelling/grammer issues just add to the feel that your post was a pissed off rant. My own typing goes to crap if I'm in a rage. The key is to wait a period of time to cool off and go back over the post and fix the errors before you send it, that's all.
Also, how precisely did temporary downtimes prevent deploys? At best, it appears they would've been delayed by a couple hours, and the great part about Git is that you can work around something like that pretty easily. Granted, downtime is annoying, but his extended difficulties seem to largely stem from his own mistakes, and for $7/month he's not exactly paying top dollar to guarantee uptime.
Learn too spell: http://iampaddy.com/spell/