4 ms·
> It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of o
by cmckn 5y ago
> It's basically a lost day of productivity even if GH goes down for only 30 minutes. Yes, we can continue coding locally, but issues & PRs are a huge part of our daily process.
I know outages are frustrating, but how does 30 minutes before 10am ruin an entire day? Maybe you’re just being hyperbolic, but people take coffee breaks longer than that.
- bob1029 5y ago> how does 30 minutes before 10am ruin an entire day? Not everyone is on pacific time. This impacted us right in the middle of a standup call and disrupted our planning for the day. Also, the problem is more that you don't know how long the outage is going to last at first, so you start finding other ways to occupy your time. Through the lens of hindsight, yes we are certainly being hyperbolic in those cases where it was only 30 minutes.
- jimmaswell 5y ago> so you start finding other ways to occupy your time Ok, pick a ticket and do some work on it locally, when that's done do the same with another. I can go a full day without interacting with github because I'm working on a local branch. Make a note of what branches you need to push later. I can't possibly imagine throwing my arms up and saying the day is wasted because I have to work locally. It's completely unbelievable.
- jorams 5y agoI understand your point and agree, but "pick a ticket" can be hard if you use GitHub issues for those.
- ipaddr 5y agoYou could use jira for tickets. Why put all your eggs in one basket?
- lallysingh 5y agoBecause the Jira basket is burning excrement.
- geoduck14 5y ago>Because the Jira basket is burning excrement. This is going to be my Slack status tomorrow.