30 ESSAYS THAT SHAPED TECH, BUSINESS AND ECONOMICS

These are the 30 essays that shaped how the technology and finance industries actually think — organized into three parts: platform strategy and aggregation, software engineering, and macroeconomics. Most of the frameworks operators and investors use daily — aggregation, CAC/LTV, innovation tokens, "this time is different" — trace back to a single post on this list. Each entry covers what the piece argued and why it became canon.

A note on scope: not everything here is strictly a blog post. The list includes a Turing Award lecture, two academic papers, and a 1930 essay — included because they circulate the same way blog posts do, passed link-to-link as required reading.

Part 1: The Platform Playbook

The vocabulary of modern digital strategy — aggregators, marketplaces, network effects, platform economics — was largely built in public, on blogs, by the people listed below.

Aggregation Theory

Ben Thompson, Stratechery (2015). The internet drove distribution costs to zero, which shifted market power away from companies that control supply and toward platforms that aggregate demand — Google, Netflix, Uber. A decade on, it remains the default operating framework for analyzing internet business models, and most strategy writing since is a footnote to it.

The Bill Gates Line

Ben Thompson, Stratechery (2018). Builds on a Gates quote to define what a platform actually is: an ecosystem where the economic value created for third parties exceeds the value captured by the host. The line cleanly separates true platforms (Windows, Shopify) from aggregators that merely host developers (iOS, Facebook) — a distinction most "platform" pitch decks still fail.

All Markets Are Not Created Equal

Bill Gurley, Above the Crowd (2012). A ten-factor framework for judging whether a two-sided marketplace can scale and sustain margin — fragmentation, frequency, payment flow, and so on. It became standard venture diligence vocabulary and is still the first filter applied to marketplace startups.

How to Kickstart and Scale a Marketplace Business

Lenny Rachitsky, Lenny's Newsletter (2020). A multi-part series built from interviews with early employees at Airbnb, Etsy, TaskRabbit and others on how they actually solved the chicken-and-egg problem — which side to seed first, which levers worked, and how few of them each company really used. It connected network-effect theory to documented tactics.

The Next Feature Fallacy

Andrew Chen (2015). Engagement problems are rarely fixed by shipping one more feature, because most users churn before they would ever encounter it. The data-backed argument redirected product teams from feature backlogs to activation funnels.

SaaS Metrics 2.0

David Skok, For Entrepreneurs (2013). The algebraic guide to subscription economics: CAC, LTV, churn, months-to-recover-CAC, and the relationships between them. It codified the financial vocabulary the entire SaaS industry now reports in.

The Cadence: How to Operate a SaaS Startup

David Sacks, Craft Ventures (2020). An operating manual that syncs product releases, sales quotas, marketing, and finance into a single quarterly rhythm. It became the default answer to "how do we run this company" for SaaS founders scaling past product-market fit.

The Third Wave of SaaS

Tomasz Tunguz (2020). Maps the evolution of software from workflow tracking to systems that act on data — anticipating the shift toward data-intensive, increasingly automated SaaS that the AI era accelerated.

The Anatomy of a Managed Marketplace

Li Jin, Andreessen Horowitz (2018). Documents the shift from un-vetted classifieds toward marketplaces that take operational control of the transaction — vetting, pricing, logistics, guarantees — to manufacture trust. It mapped the design space that produced Airbnb-class and StockX-class outcomes.

Come for the Tool, Stay for the Network

Chris Dixon, a16z (2015). Bootstrap a network by first shipping a single-player tool with standalone value — Instagram's filters — then layering the network on top of an existing user base. A four-paragraph post that became a permanent entry in the go-to-market playbook.

Part 2: Software Engineering

The engineering canon is less about technique than judgment: when to trust abstractions, when to choose boring tools, and what actually scales.

How Discord Stores Trillions of Messages

Bo Ingram, Discord Engineering (2023). The migration story from Cassandra to ScyllaDB at trillion-row scale, without user-facing interruption — hot partitions, the Rust data-services layer, and the cutover plan. Widely cited as the reference case study for large-scale storage migration.

The Bitter Lesson

Rich Sutton (2019). Seventy years of AI research show that general methods leveraging computation — search and learning — ultimately beat approaches built on hand-coded human knowledge. Written before the generative AI wave, it is the single most-cited explanation of why scaling won.

Don't Call Yourself a Programmer

Patrick McKenzie (2011). Engineers are not paid to write code; they are paid to create business value, and should negotiate, interview, and plan careers accordingly. It reframed career strategy for a generation of developers.

The Absolute Minimum Every Software Developer Must Know About Unicode

Joel Spolsky, Joel on Software (2003). Character sets, encodings, and why "plain text" does not exist. More than twenty years later it is still the document handed to new engineers when strings break across systems.

Summary of the Amazon S3 Service Disruption

AWS Engineering (2017). The root-cause analysis after a mistyped command during routine debugging removed too much S3 capacity and degraded a large fraction of the web for hours. Its candor set the baseline for public incident reports and helped normalize blameless postmortem culture.

Choose Boring Technology

Dan McKinley (2015). Companies get a small number of "innovation tokens" — spend them on the business problem, not on unproven databases. The standing corrective against stack novelty, quoted in architecture reviews ever since.

The Law of Leaky Abstractions

Joel Spolsky, Joel on Software (2002). All non-trivial abstractions leak: the messy reality underneath eventually surfaces and must be debugged. It explains why higher-level tools raise the ceiling of what engineers build without removing the need to understand the layers below.

Product vs. Feature Teams

Marty Cagan, Silicon Valley Product Group (2019). Distinguishes teams empowered to solve business problems from teams that build executive-specified feature lists. The vocabulary it introduced now structures how tech organizations talk about product culture.

Reflections on Trusting Trust

Ken Thompson, Turing Award lecture (1984). Demonstrates that a compiler can insert a backdoor into the binaries it produces — including its own — leaving nothing visible in source code. The founding document of software supply-chain security, and the reason "you can't trust code you didn't totally create yourself" is a security axiom.

How Big Tech Runs Tech Projects and the Curious Absence of Scrum

Gergely Orosz, The Pragmatic Engineer (2021). A survey of roughly 100 companies showing that the largest tech companies mostly skip prescriptive Scrum in favor of letting teams choose how they ship. It gave engineering leaders the data to cut process overhead.

Part 3: Macroeconomics

The macro canon is older and the lesson is consistent: systems fail when their participants convince themselves the old rules no longer apply.

Economic Possibilities for our Grandchildren

John Maynard Keynes (1930). Predicted that within a century, compounding capital and technology would shrink the workweek to 15 hours. The prediction half-failed in an instructive way — productivity arrived, leisure didn't — which is why it anchors every serious debate about automation and work, AI included.

The Use of Knowledge in Society

Friedrich Hayek (1945). Knowledge is fragmented across millions of individuals, so no central planner can match the price system, which aggregates that dispersed information automatically. The foundational argument for decentralized markets — and, read today, an early theory of distributed information processing.

The Return of Depression Economics

Paul Krugman, Foreign Affairs (1999). Drawing on the Asian Financial Crisis, Krugman argued that demand shortfalls and liquidity traps were not historical relics. The framework looked alarmist in 1999 and became the standard lens for understanding 2008.

The Death of Inflation?

The Economist (1996). The structural case — globalization, supply-chain efficiency, central bank credibility — for why inflation was finished as a macro force. It defined the intellectual baseline of the Great Moderation, and rereading it after 2021–22 is a lesson in how durable consensus gets falsified.

This Time Is Different: A Panoramic View of Eight Centuries of Financial Crises

Carmen Reinhart & Kenneth Rogoff, NBER (2008). Eight hundred years of data showing that every credit bubble rests on the belief that new conditions have repealed the old rules. Published as the subprime crisis broke, it removed the excuse from "nobody could have known."

The Psychology of Money

Morgan Housel, Collaborative Fund (2018). Twenty short lessons arguing that financial outcomes are driven less by analysis than by behavior — patience, ego, room for error, and the stories people tell themselves. One of the most-shared finance essays ever written, later expanded into the book of the same name.

The Rise and Fall of American Growth

Robert J. Gordon (2016). The argument that 1870–1970 — electricity, sanitation, internal combustion — was a one-time special century that digital technology has not matched in measured productivity. The strongest data-driven case for structural stagnation, and the thesis every techno-optimist argument has to answer.

Global Supply Chains in a Post-Pandemic World

Willy C. Shih, Harvard Business Review (2020). The teardown of just-in-time logistics after COVID exposed its fragility, and the roadmap toward diversified, regionalized networks. It described in advance the re-shoring and tariff re-routing that defined trade in the mid-2020s.

AI Will Transform the Global Economy. Let's Make Sure It Benefits Humanity.

Kristalina Georgieva, IMF (2024). The IMF's modeling of AI exposure: almost 40% of global employment — 60% in advanced economies — is exposed to AI, with effects split between augmentation and displacement. It moved the AI-and-labor conversation from speculation to fiscal-institution modeling.

Geopolitics and Its Impact on Global Trade and the Dollar

Gita Gopinath, IMF (2024). Documents trade and investment flows re-routing along geopolitical lines — trade restrictions tripling since 2019, FDI fragmenting into blocs — and assesses what that means for dollar dominance. The reference framework for analyzing economic fragmentation and reserve-currency risk.

---

Further reading:

• Business Hub — our full coverage of strategy and execution for operators
• The Economics of AI Infrastructure — how compute, capital and energy are reshaping competition in AI
• Platform Economics — why platforms capture disproportionate value
• Network Effects — the mechanics behind winner-take-most markets