3 ms·
if all 60 are working together sure, but if it's a handful of devs working with each other, you can pull directly from each others repository. PITB, yes. But y
by balls187 13y ago
if all 60 are working together sure, but if it's a handful of devs working with each other, you can pull directly from each others repository.
PITB, yes.
But you can still get work done.
- king_magic 13y agoAgain, not so easy when it's a massive multi-team effort - we have a continuous integration system that builds every branch (we use a GitFlow based model) on every commit that gets pushed to GitHub.
- coryking 13y agoYou can pull from eachother, but since you know github will be up in a few hours and it would take more than that to really coordinate any workflow change, most of the time people just goof off until github is back. Plus you are forgetting that lot of automated jobs get triggered on github changes. Many shops kick off all kinds of tests, deployments, and other things based on changes to the github repo.
- balls187 13y agoIf devs want to use that as an excuse to do other things, that's cool. My point was simply that you can still be productive when github goes down, if you want to be.
- king_magic 13y agoSure, developers can still be productive. But what about QA, UX, Product Managers? They rely on automated jobs that get triggered by GitHub changes. I don't think you're "wrong" for the developer use case, but the reality is that it can bring large teams to a screeching halt.