Technology Half-Life Model

Technology half-life is the time for a tool or skill to lose half its practical value. Different layers have dramatically different half-lives: fundamental concepts (algorithms, data structures) last 20-50+ years; languages and platforms last 10-20 years; frameworks and libraries last 3-7 years; specific tool configurations and APIs last 1-3 years. The implication: mastering a specific tool's configuration (1-3 year half-life) yields less long-term return than learning foundational concepts (20-50 year half-life). Professionals investing in fundamentals adapt to new tools easily; those investing only in specific tools face repeated obsolescence.

When to use it

When deciding which technology skills to invest in learning. When evaluating candidates based on technical skills versus foundational knowledge. When planning a technology stack and wanting to minimize future migration costs. When feeling anxiety about new technology trends and wondering whether you need to learn them.

How it can help

For knowledge workers investing in technology skills: invest primarily in long half-life skills (systems thinking, data structures, design patterns) and learn specific tools as needed. For hiring, value strong fundamentals over specific current-tool experience. For technology bets, assess likely half-life of each stack component and plan replacements. The model prevents over-investing in soon-to-be-obsolete skills while ensuring a foundation that transfers across tool generations.