In the fast-paced world of software engineering, we are conditioned to believe that "newest" means "best." We scroll through tech blogs and social media feeds, constantly hit with flashy headlines about the latest JavaScript framework that promises to solve every problem, or a revolutionary new database engine that claims to defy the laws of physics. This relentless search for the cutting edge creates a constant sense of anxiety. We worry that if we aren't learning the tool that launched last Tuesday, we are already becoming obsolete. We treat technology like milk, assuming it has a strict expiration date and that anything sitting on the shelf for too long must be turning sour.
However, there is a counter-intuitive principle which suggests we should look backward to see the future. This concept, known as Lindy’s Law or the Lindy Effect, proposes that for non-perishable things like ideas, books, or software, the passage of time works in reverse. Instead of wearing out, these things gain life expectancy as they age. Every year that a specific technology survives, it proves its resilience against competitors, bugs, and shifting market trends. By understanding this mathematical quirk of longevity, we can stop chasing every passing fad and start building our careers and projects on foundations that are actually built to last.
At its heart, Lindy’s Law is based on a power law probability distribution, a mathematical pattern used to predict how long something will last. While humans and washing machines have a clear "sell-by" date due to physical decay, information does not. If you meet a 90-year-old man, you can reasonably guess he might live another five or ten years, but certainly not another 90. His chance of survival decreases every day because his "parts" are wearing out. In contrast, if a book has been in print for 50 years, Lindy’s Law suggests it will likely be in print for another 50. If it survives those next 50, its life expectancy actually doubles again.
This happens because the world acts as a brutal filter for ideas. Most new concepts fail almost immediately. They are either flawed, unhelpful, or simply outshined by something better. When a technology like the C programming language or the SQL database survives for decades, it isn't just luck. It is because that tool has survived thousands of attempts to replace it. It has been tested in millions of edge cases, and its flaws are well-documented and manageable. The longer it stays relevant, the more "anti-fragile" it becomes, gathering a massive ecosystem of guides, libraries, and experts that make it even harder to displace.
To apply this law correctly, we must be careful to distinguish between a physical object and the information it carries. Lindy’s Law applies only to the "non-perishable." Your laptop is a perishable item; it will eventually suffer from hardware failure, a dying battery, or a cracked screen. It follows a traditional life expectancy curve where it gets closer to death every day. However, the operating system kernel or the mathematical algorithms running on that laptop are non-perishable. They are patterns of information that do not "rot" like biological things.
In the tech industry, we often mix up these two categories. We assume that because our hardware needs upgrading every three years, our software choices should follow the same cycle. This leads to "Resume-Driven Development," where engineers choose the newest, riskiest tools just to stay relevant, even if those tools are less stable than the "boring" alternatives. By recognizing that the Linux kernel or the TCP/IP protocol, the standard for internet communication, are Lindy-compatible, we can invest our time in learning underlying principles that will likely be the same 20 years from now. This is better than memorizing the rules of a framework that might be dead by Christmas.
When we look at the landscape of modern software, we see Lindy’s Law in action everywhere. Consider the tools that form the "boring" backbone of the internet. These are the winners of a decades-long evolutionary war. They have survived market crashes, the rise of mobile devices, and the migration to the cloud. While they might not be the topic of every keynote speech at a trendy conference, they are the tools that businesses rely on when failure is not an option.
| Technology Type | High Lindy (The Survivors) | Low Lindy (The Newcomers) |
|---|---|---|
| Data Storage | SQL (PostgreSQL, MySQL) | Recent "NoSQL" flash-in-the-pans |
| Languages | C, Java, Python, C++ | This year's niche functional language |
| Protocols | TCP/IP, HTTP, DNS | Experimental proprietary mesh protocols |
| Text Editing | Vim, Emacs | Flashy, VC-funded closed-source editors |
| Operating Systems | Unix-like (Linux, BSD) | Experimental micro-kernels |
As the table shows, the "High Lindy" options are often open-source, community-driven, and based on simple, powerful concepts. They are the stable choices. Choosing PostgreSQL for a new project is a "Lindy" move because SQL has been the dominant way to handle data since the 1970s. Choosing a brand-new, venture-backed database that was released 18 months ago is a high-risk gamble. According to the law, that new database has a much higher statistical chance of being abandoned or replaced than the 40-year-old veteran has of disappearing.
If you are a student or a professional looking to get the most out of your study time, Lindy’s Law offers a clear strategy: focus on the "evergreens." If you spend six months learning every detail of a specific, trendy JavaScript library, that knowledge might be useless in three years. However, if you spend those six months mastering data structures, algorithms, or the fundamentals of networking, that knowledge will serve you for the rest of your career. These are the Lindy concepts of computer science; they have been the foundation of the field for half a century and show no signs of going away.
This doesn't mean we should never use new things. Innovation is necessary, and every "Lindy" survivor was once a "new" tool. However, it helps us measure our risk. If you are building a critical system that needs to work for the next ten years, you should lean heavily on stable, Lindy-tested technologies. If you are building a small prototype or a side project, that is the perfect time to play with newcomers. The goal is to avoid building a massive, long-term project on a foundation of "sand" that has not yet been tested by the tides of time.
Skepticism is often mistaken for being old-fashioned or out of touch, but in the context of Lindy’s Law, skepticism is actually a rational, mathematical stance. The "Hype Cycle" often drives us toward tools that are at the peak of inflated expectations. By the time a technology reaches the "Plateau of Productivity," the stage where it is widely understood and useful, it has already begun its journey toward becoming a stable survivor. The trick is to identify when a technology has shifted from a fad to a fixture. Usually, this happens when the initial excitement dies down, but the tool remains in heavy use because it solves a fundamental problem effectively.
Think of the "dependency hell" that plagues modern web development, where projects rely on hundreds of external pieces of code. Many projects break because they rely on dozens of tiny, new libraries maintained by a single person who might lose interest next week. A "Lindy" approach to architecture involves minimizing these fragile dependencies and relying on the standard libraries of established languages. It is the difference between building a house out of modular plastic blocks that might go out of production and building a house out of stone. The stone might be heavier and harder to work with at first, but you know exactly how it will behave centuries from now.
The beauty of Lindy’s Law is that it gives you permission to slow down. You don't have to be a pioneer on every single front. By anchoring your work in time-tested principles and technologies, you ensure that your creations have the best possible chance of lasting. When you choose the "old" tool that works, you aren't being lazy; you are being a strategist. You are betting on the collective wisdom of thousands of engineers who came before you. May your future projects be built on such solid ground, and may your curiosity lead you to discover the timeless ideas that will still be relevant long after current trends have faded into history.
Software & App Development
What you will learn in this nib : You’ll learn how to spot and focus on timeless programming tools and core concepts so you can build lasting projects and a resilient career without chasing every fleeting tech hype.