Inside the longest Atlassian outage

Re:Inside the longest Atlassian outage by robertlagrant on Wednesday April 13, 2022 @03:13PM (#31018926)

Not in a negative way. You want to trust engineers to always have changes built and tested before they go to production, but when something egregious happens you need to go back and see what went wrong. You can choose to interpret that as control, but really the only alternative (often cited) is "Well that shouldn't ever happen, so you don't need tooling to support that situation".

And that is not a useful way of thinking when you have real engineers writing software that people depend on.

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by malermeister on Wednesday April 13, 2022 @03:58PM (#31019509)

I think the problem is that the processes are often not mutually agreed, but instead dictated by middle managers.

JIRA then becomes a tool for enforcing arbitrary rules, e.g. control

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by robertlagrant on Wednesday April 13, 2022 @04:29PM (#31019846)

This is very likely even if engineers come up with the processes, unless all process is scrapped and done from scratch every time an engineer is hired.

[ Parent | on HN ]