[koliber]

It kind of already happens to devs when Jira or GitHub goes down. These tools are part of the core process of software delivery for many dev teams.

When the forklift breaks, you can't load the truck.

[koolba]

The JIRA example is a funny one. It’s like a workshop with a broken clipboard. Imagine not ordering a replacement one because there’s no task (written on said clipboard) to order a replacement.

[sshine]

I can easily imagine this.

I have to have a piece of paper on my desk in front of my computer.

I write my priorities there. If I don't, I find it extremely hard to concentrate on or prioritise anything.

What's problematic about depending on Jira this way is:

When Jira is down, you can't go to your supplies stash and get another Jira.

Programmers can work when the office Internet or GitHub is down, because git is decentralised.

Managers don't seem to factor in that kind of risk when they subscribe to a critical tool into the cloud.

[aaomidi]

Because how often is the internet down?

If you’re in an office you’re absolutely supposed to be getting multiple upstream connections.

[koolba]

The local internet connection is a necessary but not sufficient part of accessing any hosted service. More importantly, the service itself has to be online.

[aaomidi]

Most of these SaaS services have enough availability to practically not be a problem.

[sshine]

In the last year, if I accumulate all service outages at GitHub and at my office’s ISP, I think GitHub was out of reach for more than a couple of hours five times.

[aaomidi]

GitHub is an anomaly tbh.

[sshine]

GitHub has a satisfying uptime, compared.

Most incidents were related to local Internet.

Regardless, I didn't take a break until GitHub came back.

I shouldn't have to take a break from planning just because Jira is down.