The Lindy Effect: Time-Tested Wisdom Over Novelty
The Lindy Effect: Time-Tested Wisdom Over Novelty
The Core Idea
The Lindy Effect is a counterintuitive concept: the future life expectancy of non-perishable things (ideas, technologies, books) is proportional to their current age.
In other words, things that have been around for a long time are likely to be around for much longer, while new things are more likely to disappear quickly.
A book that’s been in print for 100 years is likely to remain relevant for another 100 years. A programming paradigm that’s been used for 50 years will probably be useful for another 50. But the hot new framework released last month? Its expected lifespan is… about a month.
This principle, popularized by Nassim Nicholas Taleb in Antifragile, offers a powerful filter for where to invest your time, energy, and attention in a world drowning in novelty.
Origins and Context
The concept emerged from observations about Broadway shows in the 1960s: a show that had been running for 100 days was likely to run another 100 days, while one that opened yesterday might close next week. The name “Lindy” comes from Lindy’s delicatessen in New York, where comedians would gather and discuss which acts would last.
Mathematician Benoît Mandelbrot formalized the mathematical underpinning, and Taleb extended it to ideas, technologies, and knowledge itself.
Critical distinction: The Lindy Effect applies only to non-perishable things—ideas, technologies, institutions, books. It doesn’t apply to living organisms (humans don’t become more likely to live longer the older they get; quite the opposite).
Why It Works: Time as a Filter
Time is the ultimate stress test. Ideas and technologies that survive decades do so because they’ve been exposed to countless challenges, criticisms, refutations, and alternatives—and withstood them all.
Consider programming languages:
- C (1972, 53 years old): Expected to remain relevant for decades more
- Python (1991, 34 years old): Likely to be around for another 30+ years
- Rust (2015, 10 years old): Probably useful for another 10+ years, but higher variance
- That new language from 2024: Expected lifespan is ~1 year unless proven otherwise
This isn’t about age bias—it’s about survival bias as signal. Old things survived because they work across different contexts, cultures, and use cases. New things haven’t been tested yet.
Practical Applications for Principal Engineers
1. Technology Investment Decisions
Scenario: Choosing between established and novel technologies for a critical system
Lindy Lens:
- PostgreSQL (25+ years) vs NewScaleDB (2 years): PostgreSQL has survived NoSQL hype, cloud transitions, and countless competitors. Its longevity suggests stability and continued relevance.
- REST APIs (20+ years) vs GraphQL (8 years) vs Latest protocol (1 year): Older doesn’t mean always better, but Lindy suggests REST will outlast most alternatives for general-purpose APIs.
Application: For mission-critical systems with 10+ year horizons, favor technologies with 10+ year track records. The newer technology must offer dramatic advantages to justify the higher risk.
2. Learning Strategy
The Problem: Infinite learning options, finite time. What should a principal engineer master?
Lindy-Guided Learning Hierarchy:
Tier 1 - Timeless (50+ years, highest ROI):
- Algorithms and data structures
- Networking fundamentals (TCP/IP, HTTP)
- Operating systems concepts (processes, memory, I/O)
- Relational database theory
- Software design principles (coupling, cohesion, abstraction)
Tier 2 - Durable (10-25 years, high ROI):
- Object-oriented and functional programming paradigms
- Distributed systems patterns
- Security fundamentals (cryptography, auth models)
- Domain-driven design
- Unix philosophy and tools
Tier 3 - Contemporary (5-10 years, medium ROI):
- Current cloud platforms (AWS, Azure, GCP)
- Container orchestration (Kubernetes)
- Modern languages (Rust, Go, TypeScript)
- CI/CD practices
Tier 4 - Emerging (<5 years, speculative ROI):
- Latest frameworks, libraries, tools
- Bleeding-edge paradigms
Strategy: Invest 60% in Tier 1-2, 30% in Tier 3, 10% in Tier 4. Master the timeless before chasing the trendy.
3. Career Development
Lindy Skills for Technical Leaders:
High Lindy (durable across decades):
- Writing clearly: Technical writing, documentation, RFCs
- Communication: Explaining complex concepts simply
- Mentoring: Developing others
- Decision-making under uncertainty: Judgment and trade-off analysis
- Systems thinking: Understanding interconnections and second-order effects
Low Lindy (tool/trend-dependent):
- Specific framework expertise (React hooks, Angular directives)
- Vendor-specific certifications
- Narrow technical specializations that could be automated
Insight: Invest heavily in high-Lindy skills. They compound across your entire career and transfer across contexts. Low-Lindy skills have their place (you need to deliver today), but don’t mistake proficiency in the hot framework for durable expertise.
4. Architectural Principles
Lindy-Tested Architecture Wisdom:
Survived decades:
- Separation of concerns: Modularity, layering, boundaries
- Loose coupling, high cohesion: Minimize dependencies
- Simplicity: Prefer boring solutions that work
- Fail-safe defaults: Secure by default, opt-in to risk
- Data outlives code: Invest in data models more than implementation
Recently popular (jury still out):
- Microservices everywhere
- Serverless-first architecture
- Event sourcing by default
Application: When designing systems intended to last 10+ years, lean heavily on principles with 20+ year track records. Experiment with newer patterns, but don’t bet the company on them.
The Lindy Effect and Wisdom Literature
Philosophy and Self-Development:
Books that have survived centuries offer higher signal-to-noise ratio than this month’s bestseller. Why?
- Survivorship filter: Bad ideas get forgotten; valuable insights get retransmitted across generations
- Context independence: Ideas that work across cultures and eras are more fundamental
- Compound testing: Millions of readers have tested and validated the insights
High Lindy Reading:
- Stoic philosophy (Marcus Aurelius, Seneca, Epictetus - 2000+ years): Timeless wisdom on dealing with adversity, controlling emotions, and focusing on what you can control
- Montaigne’s Essays (450+ years): Self-reflection, skepticism, and human nature
- Shakespeare (400+ years): Human psychology and relationships
Contrast with: Self-help bestseller from 2024 (expected lifespan: 1-2 years)
Implication for principal engineers: Read old books. They’ve been debugged by time. The latest productivity hack might work or might be debunked next year. Stoic principles about controlling attention and managing stress? Proven across millennia.
Limitations and Nuances
The Lindy Effect Is Not Universal
Where Lindy doesn’t apply:
- Perishable goods: People, animals, physical objects
- Fast-changing domains: When underlying substrate changes completely (e.g., quantum computing may invalidate classical computing assumptions)
- Path dependencies: Sometimes inferior technologies win due to network effects (QWERTY keyboards)
Lindy ≠ Optimal
Something surviving doesn’t mean it’s best—it means it’s good enough to persist. TCP/IP has Lindy, but it has known limitations. SQL databases have Lindy, but they’re not ideal for every use case.
The wisdom: Use Lindy for risk assessment, not optimization. Old technologies are lower risk (known failure modes, mature tooling) but may not be optimal for every scenario.
Innovation Still Matters
The Lindy Effect isn’t an argument against innovation—it’s a framework for risk management. New technologies create the next generation of Lindy winners.
Balanced approach:
- Core systems: Favor high-Lindy choices (proven, stable)
- Experimental projects: Test low-Lindy options (learn, explore)
- Greenfield with longevity: Choose technologies at least 5-7 years old (proven but still modern)
Living by Lindy: Practical Implementation
1. The 10-Year Rule
Before adopting a new technology for a critical system, ask:
- “Will this still be used 10 years from now?”
- “How long has this existed, and how many contexts has it survived?”
If the technology is younger than 5 years, it needs extraordinary justification.
2. The Reading Filter
For professional development:
- 50% of reading from books 10+ years old
- 30% from books 3-10 years old
- 20% from recent material (papers, articles, new books)
For technical skills:
- 60% on fundamentals (timeless)
- 30% on established modern practices (5-10 years)
- 10% on bleeding edge (awareness, not mastery)
3. The Advice Filter
When receiving career or life advice, weight it by Lindy:
- Advice from someone with 20+ years experience > advice from 2-year expert
- Wisdom that’s been given across generations > latest productivity trend
- Principles that apply across industries > hyper-specific tactics
4. Building Your Own Lindy
Create knowledge and systems that could become Lindy:
- Document principles, not just implementations
- Write code that’s simple and comprehensible (more likely to survive)
- Build on stable foundations
- Solve fundamental problems, not just symptoms
Reflection Questions
For your current work:
- What percentage of your tech stack would you describe as “high Lindy” (10+ years old and proven)?
- Are you investing learning time in fundamentals that will be relevant in 20 years, or chasing the latest trends?
- When was the last time you read a technical book published before 2000? Before 1990?
For your career:
- What skills are you building that will still be valuable in 15 years?
- Are you becoming an expert in timeless principles or in transient tools?
- What wisdom from experienced engineers have you dismissed as “old-fashioned” that might actually be Lindy-tested truth?
For life:
- What books have you read that have been around for 50+ years? 100+ years?
- What life advice have you received from multiple older people across different contexts? (That’s Lindy speaking)
- Are you optimizing for what’s fashionable or what’s proven to work across time?
Conclusion
In a field obsessed with novelty, the Lindy Effect is a radical idea: old is often better than new, and proven is safer than innovative.
This doesn’t mean never innovate or never try new things. It means calibrating risk appropriately. For critical systems, career-defining skills, and foundational knowledge, favor what’s survived decades of testing. For experiments, side projects, and exploration, embrace the new.
The tech industry suffers from chronic novelty bias—every new framework is “revolutionary,” every new paradigm will “change everything.” Lindy offers an antidote: respect what has survived. The old boring technology stack probably became old because it works. The ancient philosophical text probably survived because it captures something true about human nature.
Time is the ultimate validator. Use it as a filter, and you’ll waste less effort on passing fads and invest more in what endures.
As Taleb writes: “If a book has been in print for forty years, I can expect it to be in print for another forty years. But, and that is the main difference, if it survives another decade, then it will be expected to be in print another fifty years.”
Choose Lindy. Learn the old. Build for longevity. The newest isn’t always the best, but what has endured usually has something to teach.