Quotes from the Cloudiest WebScaliest DevOps Teams

We can define the process precisely with Natural Deduction using the inference rules. This probably seems a bit obtuse, but so is the bash code that actually implements it! They’re confusing in very different ways so… hopefully if something doesn’t make sense in one presentation, it will in the other! Got it?

Eng 2: I was like "right, right, yes, very good" until I got to this bit:

> but so is the bash code that actually implements it

Monsters!

Eng 1: I thought everybody wrote shell scripts when they were trying to prune blatantly absurd dependencies from their transitive closures?

"Kinesis isn't, is it?"

"Everything's dead, Dave!"

"Not Cloudwatch!"

"Gordon Bennett! Yes, Cloudwatch. Everything. Everything's dead, Dave!"

"Athena?"

It's dead, Dave. Everything is dead. Everything is dead, Dave."

Eng2: [2:06 AM] Yep. We need to run this and GTFO. AWS support have said: "hey I just talked to an expert, since you will be sending almost 300 request per second we don't currently foresee any limitation it could cause however we do recommend to implement a retry logic so as if request fails you can retry."

Expert has signed off on it. We're onto a winner

Eng1: [2:07 AM] Yeah you write retry logic for a distributed shell script run by a for loop at 2:07 am