How LinkedIn Handles Merging Code In High-velocity Repositories

- Niket Parikh tl;dr: This post focuses on how the CI system works with repositories of different sizes, "specifically ones with a high velocity of commits being merged into master, to ensure timeliness and code correctness."

featured in #182

When Scaling Your Workload Is A Matter Of Saving Lives

- Werner Vogels tl;dr: Werner received a call to scale the data model that governors were using to plan their response to COVID-19. He talks through how he did so with the Amazon team. 

featured in #180

Scaling To 100k Users

- Alex Pareto tl;dr: There isn't much documentation on the technical challenges that occur due to rapid growth. Alex has done this several times and distilled what he's learnt here.

featured in #173

Work Is Work

tl;dr: Org design is fetishized by corporate America always looking for some hack. There isn't one. Organizations are imperfect and, at very best, scale linearly. Despite that, there are tips on how to design a scaling organization here.

featured in #169

Building The DataDog Platform For Processing Timeseries Data At Massive Scale

- Vadim Semenov tl;dr: Podcast interview with Vadim Semenov discussing "the systems that DataDog has built to power their business, and how their teams are organized to allow for rapid growth and massive scale." 

featured in #167

Speed At Scale - What's New In Web Performance?

- Katie Hempenius Addy Osmani tl;dr: (1) Lighthouse supports Performance Budgeting (2) Native image and iframe lazy-loading comes to the web (3) Google Fonts now supports font-display as a query parameter.

featured in #143

Python at Netflix

tl;dr: High-level run through of how Python is used in the content life-cycle at Netflix along with mentions of the open-source packages used.

featured in #139

How Is Software Developed At Amazon?

- Todd Hoff tl;dr: Fireside chat with Ken Exner, GM at AWS Dev Tools. The article summarizes it more extensively than I will. Key ideas are: Create more autonomy and higher velocity by moving away from monolithic architecture towards microservices and two pizza teams 🍕🍕 Automate everything Culture of ownership and accountability. Two pizza teams own everything relevant to their product. They acts like startups, managers oversee startups Are the short summaries (tl;dr sections) helpful? Please vote here

featured in #131