Inside the longest Atlassian outage

Re:Inside the longest Atlassian outage by TheJoeMan on Wednesday April 13, 2022 @12:30PM (#31016721)

I suppose that’s why you don’t combine a tazer and gun into 1 device with 2 triggers.

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by mrits on Wednesday April 13, 2022 @12:57PM (#31017068)

If you have a 3rd trigger where the gun turns on the user it would be fairly safe.

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by femiagbabiaka on Wednesday April 13, 2022 @02:37PM (#31018456)

the problem is that sometimes that gun looks like a taser.

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by dylan604 on Wednesday April 13, 2022 @12:47PM (#31016945)

Instead, you make it with one trigger and a PRNG that decides which gets activated. Just hope you've chosen the right PRNG!!

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by tadfisher on Wednesday April 13, 2022 @01:12PM (#31017260)

I will then write a script calls your script with the PRNG of my choice: PRNG1 always returns "trigger 2", and PRNG2 always returns "trigger 1". This detail will be documented in Confluence.

[ Parent | on HN ]

Re:Inside the longest Atlassian outage by rubyist5eva on Wednesday April 13, 2022 @01:32PM (#31017540)

Considering American police can't even seem to get it right when they have two distinct firearms, and are trained to holster them on specific sides so they know what they are grabbing - and still manage to f*ck it up....this might be an improvement.

[ Parent | on HN ]