Our systems are offline, and we don’t know what to do. Typically when we have a problem, we ask the system how to solve it, but it says it’s unavailable. We have tried asking each other, but nobody knows what to ask exactly.
Our systems are offline, and we don’t know what to do. Typically when we have a problem, we ask the system how to solve it, but it says it’s unavailable. We have tried asking each other, but nobody knows what to ask exactly.
And now, on to heating our dinner with friction.
The winner gets all the computational resources, gets more money, and repeat.
When the forklift breaks, you can't load the truck.
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.
If you’re in an office you’re absolutely supposed to be getting multiple upstream connections.
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.
Edit: apparently not based on the sibling comment.