"My teammates have tons of experience, and there is a clear “every man for himself” mentality. Most of them have big egos and really rotten and bitter attitudes. They are stars, they know it, and treat people who are not at the same level like idiots (like idiot me)."
I'd get the fuck out of there as fast as possible. With that kind of environment, it is only a matter of time before it crashes and burns.
The github service is nice, but do you really want to put your [code|website|etc] somewhere that can become inaccessible if some [person|group|criminal|government] decides they don't like something about it?
What service wouldn't be susceptible to such an attack? The only way to avoid it would be to not put your [code|website|etc] on the internet. That seems a bit extreme.
It is not the DDos that I have a problem with. It is the centralization of the Internet that I have a problem with. Host your own shit, pay your own costs. This way if somebody gets pissed at you for your shit code, you don't cause problems for me and my shit code.
Yes. The nature of git means this has not stopped our workflow. Just because we can't update a central source doesn't mean we can't continue to get things done. Also, if a large enough entity doesn't like what you're doing, you're better off putting your code in Github/Bitbucket/etc because chances are you can't mitigate a DDoS of this scale by yourself.
If you host your code on this "free" service and you cause a DDos because someone doesn't like what you are doing, are you going to pay for the mitigation costs to the free provider?
I'd get the fuck out of there as fast as possible. With that kind of environment, it is only a matter of time before it crashes and burns.