featured in #171
featured in #171
The Myth Of Architect As Chess Master
- Ben Northrop tl;dr: While the rules of chess are consistent, the rules of software are not. To be an architect, you need to understand the specific "game you're in" - the business drivers, risks, technical constraints, integrations, trade-offs, and so on.featured in #170
featured in #164
featured in #162
Making Instagram.com Faster: Code Size And Execution Optimizations (Part 4)
- Glenn Conner tl;dr: The first three parts were around optimizing loading patterns. This part is about shipping less code to the user, particularly JavaScript. Click the link in this tweet if you are paywalled.featured in #162
featured in #153
Static Analysis At Scale: An Instagram Story
- Benjamin Woodruff tl;dr: The importance of static analysis and codemod (vs lint) in finding code in Instagram's monolithic Django based architecture.featured in #151
featured in #150
Growth Engineering at Netflix - Accelerating Innovation
tl;dr: Insight into the signup architecture at Netflix. An overview of the UX on mobile / TV and how the stack is configured to support this flow. If you're paywalled, click the link in this tweet.featured in #147