Making Time to Change, Part 1

- Phil Le-Brun tl;dr: The author dispels the myth that "employees simply don’t have the time to take on more work" citing organizational issues of ownership, opacity of issues, lack of emotional engagement. Phil runs through Muda, a "catch-all term for non-value-added activities."

featured in #192

AWS S3: You’re Out Of Order

- John Williams tl;dr: Seeing delays in large uploads to AWS, John discovered thousands of out-of-order packets causing retransmissions. When told this, AWS said that “out-of-order packets are not a bug." He discusses how the issue was fixed.

featured in #169

The Amazon Premium

- Cal Peterson tl;dr: Suspicious of established cloud providers actually providing value for money, Cal compares virtual machine and object storage pricing amongst the main providers. Google, AWS, Azure came out to be more expensive than the others. 

featured in #166

Andy Jassy Aims To Reinvent AWS For The Cloud’s Next Generation

- John Furrier tl;dr: Fascinating conversation with the CEO of AWS on the ongoing transformation of AWS approach in cloud computing.

featured in #164

AWS’ Sponsorship Of The Rust Project

- Arun Gupta Jacob Peddicord David Barsky tl;dr: More companies are using Rust including Google, Microsoft, and Mozilla. It's also seen growth in AWS, with services such as Lambda, EC2, and S3.

featured in #157

Modern Applications At AWS

- Werner Vogels tl;dr: Amazon adopted 5 principles to operate quicker iterative cycles - microservices, purpose-built databases, automated software release pipelines, a serverless operational model and automated, continuous security. Article discusses each one.

featured in #153

Proving Security At Scale With Automated Reasoning

- Werner Vogels tl;dr: Fascinating run-through of how AWS thinks about security at scale, starting with the Shared Responsibility Model where AWS is responsible for security of the cloud and customers are responsible for security in the cloud.

featured in #146

AWS Costs Every Programmer Should Know

- David Hatanian tl;dr: Basic guide on how to think through the AWS dollar costs to better evaluate your architectural design.

featured in #145