Simple Systems Have Less Downtime
tl;dr: Easier to manage, simpler systems require less proficiency and troubleshooting, and provide more alternatives. The post outlines three principles of simple systems.
featured in #176
What Is A Software Architect?
tl;dr: A comprehensive guide - what an architect is, various levels of architecture, typical activities, important skills, suggested books and more.
featured in #171
The Myth Of Architect As Chess Master
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
Reclaim Unreasonable Software
tl;dr: Code is "big ball of mud" at growth stage companies. Will describes a new approach to untangle it. "List all the beliefs you'd need to have to be confident in modifying your software" and see how they move up the behavior & property ladder, which he describes in detail.
featured in #162
Making Instagram.com Faster: Code Size And Execution Optimizations (Part 4)
Click the link in this tweet if you are paywalled.
featured in #162
Modern Applications At AWS
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
Static Analysis At Scale: An Instagram Story
tl;dr: The importance of static analysis and codemod (vs lint) in finding code in Instagram's monolithic Django based architecture.
featured in #151
Towards Progressive Delivery
tl;dr: Progressive Delivery is the term the author has coined for the new basket of skills and technologies concerned with modern software development, testing and deployment i.e. Canarying, Feature Flags, A/B testing at scale.
featured in #150