Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You 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.



If 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.


Sure, 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: