Link:Sean Goedecke
Core Principles for Good API Design
Sean Goedecke outlines practical principles for API design, arguing that good APIs are boring, must never break existing consumers, and should favour developer ease over theoretical purity.
Steve Yegge's Analysis: How Jeff Bezos' Service Mandate Built Amazon's Platform Edge
LinkSteve YeggeOpinion
Steve Yegge compares his six-and-a-half-year tenures at Amazon and Google. Despite extensive criticisms of Amazon's internal engineering discipline and workplace culture, he highlights one decisive advantage: Jeff Bezos' 2002 service mandate, which enforced strict service-oriented architecture and externalizable APIs across the entire company.
Key points
- Amazon vs. Google comparison: Yegge critiques Amazon's uneven hiring bars, lack of dedicated SREs, minimal employee perks, and unstandardised codebase, while praising its pubsub and library versioning systems.
- The Bezos Mandate (~2002): Teams were required to expose all data and functionality through service interfaces; direct database reads, shared memory, and backdoors were forbidden under penalty of termination.
- External by design: Every interface had to be planned and built to be safely exposed to external developers without exception.
- Strict enforcement: The initiative was overseen by Rick Dalzell, who pushed teams towards hardened interfaces across the company.
- Operational lessons learned: On-call escalations bounced across long dependency chains, peer teams acted as accidental DoS attackers requiring quotas/throttling, and monitoring converged with automated QA.
- Required platform tooling: Managing hundreds of services forced Amazon to implement universal service discovery, registration systems, and sandbox environments for debugging.
Why it matters
This text documents how top-down architectural discipline can systematically force an organization into an API-first mindset. The operational challenges Amazon encountered during its internal SOA overhaul prefigured the core tenets of modern microservices, service discovery, and cloud platforms.
Analysis
Yegge contrasts Google's strong engineering hygiene and perks with Amazon's cut-throat execution. His core argument illustrates that Amazon's architectural transformation succeeded because the mandate removed internal trust between teams, treating internal colleagues like external API consumers and turning services into platform primitives.
Mentioned links
Summary generated by AI (Gemini 3.8 Flash, 27 September 2026). It may contain errors – the original source is authoritative.
Related entries
Similar in content, found by the AI search.
X post:Sarim Malik
Principles of Good API Design: Familiarity, Stability, and Versioning
Sarim Malik shares an essay by Sean Goedecke detailing practical API design. Effective APIs should be familiar and 'boring' rather than adhering to rigid REST or HATEOAS dogmas, with backwards compatibility taking top priority.
4.1kbookmarks194.9kviews
X post:Justin Duke
Software Factories: Why the Value Lies in Org Process, Not Infrastructure
Justin Duke highlights an essay by Cole Murray exploring the concept of the 'software factory'. Murray, maintainer of the open-source platform OpenInspect, argues that agentic development systems succeed or fail based on organisational processes rather than commoditised tooling.
1kbookmarks124.8kviews
X post:Zach Lloyd
The Cultural Shift to Software Factories: Moving from Local Agents to a Central Team Setup
Zach Lloyd shares insights on adopting software factories, noting that the biggest cultural change was transitioning from individual agents running on local machines to a centralised agent setup built collaboratively by the team.
266bookmarks7.3kviews
Article:Lalit
How a Staff Engineer Finds Problems Worth Solving
Google Senior Staff Engineer Lalit explains how he identifies high-impact technical problems without relying on top-down direction. Rather than scheduling abstract brainstorming sessions, he advocates for ambient listening, letting problems accumulate over time, and uncovering the underlying patterns behind disparate user feature requests.
X post:Mahax
AI Engineering and Graph Orchestration: Jeff Dean Lecture and Guide to Agent Parallelisation
An X post by Mahax highlights a one-hour lecture by Jeff Dean spanning LLM basics to coordinating 100 AI agents. The post also references an accompanying guide on graph engineering using Claude.
3.8kbookmarks273.9kviews
Let's talk about your project
Locations
- Mattersburg
Johann Nepomuk Bergerstraße 7/2/14
7210 Mattersburg, Austria - Vienna
Ungargasse 64-66/3/404
1030 Wien, Austria
Parts of this content were created with the assistance of AI.