DEV Community

Fernando Rodriguez
Fernando Rodriguez

Posted on • Originally published at frr.dev

The Half-Life of Your Skills Is 2 Years (And Dropping)

The Layoff He Didn't See Coming

A 38-year-old senior developer. Eight years at the company. Clean code, best practices, zero production incidents.

In his last performance review, his output was 40% lower than colleagues with half his experience. The difference: they used Copilot, Cursor, and Claude Code. He kept writing every line by hand, convinced that "AI tools generate mediocre code."

He wasn't fired for writing bad code. He was fired for writing good code too slowly.

This story isn't exceptional. It's the new pattern.

Your Experience Has an Expiration Date

For decades, experience equaled value. More years meant more accumulated knowledge, and that knowledge appreciated over time. A professional with 20 years of experience was, almost by definition, more valuable than one with 5.

That equation is broken.

According to data from IBM and the World Economic Forum, the half-life of a technical skill has dropped from approximately 10 years in 1990 to less than 5 years in 2020. Current estimates place that figure below 3 years for skills related to software development, data, and artificial intelligence.

Decade Technical skill half-life
1990s ~10 years
2000s ~7 years
2010s ~5 years
2020s <3 years

In practical terms: what you learned three years ago is already losing relevance. What you mastered five years ago might be directly obsolete.

It's not about whether you're good or bad at your job. It's physics: technical knowledge depreciates, and the rate of depreciation is accelerating.

Four Questions You Should Ask Yourself Every Year

Professional obsolescence doesn't send warnings. There's no alarm that goes off when you cross the "difficult to place" threshold. There's no HR email saying "your profile is no longer competitive." One day you simply discover the market moved on and you stayed where you were.

These four questions are your early warning system. Answer them honestly. Your career depends on it.

1. Which skill I use today didn't exist three years ago?

If you don't have a clear answer, there's a problem. Because your competitors do.

While you perfected what you already knew, others were learning AI agents, RAG architectures, or deploying infrastructure with Terraform. Not because they're smarter. Because they spent time on the uncomfortable while you optimized the comfortable.

The market doesn't reward mastery of stable technologies. It rewards the ability to adopt emerging technologies before they become mandatory.

2. When was the last time I learned something genuinely difficult?

The comfort zone is where careers go to die.

Every month you spend without learning something new, someone younger and cheaper is learning it. You're not competing against your five-year-ago self. You're competing against the junior who just finished an intensive LLM course, who masters tools you haven't even tried, and who charges half what you do.

Your experience only matters if it includes recent experience. "I've been programming for 15 years" means nothing if the last 3 were doing the same thing.

3. Does my company invest in my training, or just consume my time?

There are companies that understand continuous learning is an investment. And there are companies that treat professionals like batteries: extract energy until they're depleted, then replace them.

If you've gone years without your company funding training, without allocated time for learning, without access to conferences or development resources, you have two problems. One: that's exactly how they see you—a resource to squeeze, not an asset to develop. Two: you'll pay the bill for your updates. In time. In money. Or in opportunities you'll never know you lost.

Companies that invest in training retain talent. Those that don't rotate staff until they find someone already trained. Guess who pays the cost of that rotation.

4. Could I get my current job if I applied for it today?

This is the exercise that hurts most. And that's why it's the most important.

Open LinkedIn right now. Search for jobs for your current position, in your sector, in your city. Read the requirements for five postings. Not the "nice-to-haves." The mandatory ones.

Do you meet them all? Do you master the technologies they ask for? Do you have demonstrable experience with the tools they mention? Could you answer technical interview questions about them?

Count how many requirements you don't meet. That number is your personal technical debt. And like all debt, it accrues interest. Every month that passes without settling it, it grows. Until one day you discover the market no longer wants you at any price.

The Minimum Viable Plan

Staying current requires time. But not as much time as recovering from obsolescence.

A minimum viable plan for any technical professional includes:

Active training: 2-4 hours weekly. Not passively reading articles or watching videos. Deliberate practice: courses with exercises, projects, code that works.

One certification or intensive course per year. Not for the paper, but for the process. Forcing yourself to study something new in a structured way keeps the active learning muscle engaged.

One personal project with new technology every six months. The best way to learn something is to build something with it. It doesn't have to be big. It has to be real.

Active professional network. Not passive LinkedIn. Communities where people discuss, share, ask questions. Collective knowledge moves faster than any official curriculum.

This represents approximately 5-10% of your work time. It's a significant investment, but the alternative—discovering your obsolescence when it's too late—is considerably more expensive.

It's Not the Future. It's the Present.

There's a tendency to talk about these changes as something that's "coming." As if we had time to prepare.

We don't. The change already happened.

AI is already transforming how people get hired, how they work, and which skills have value. Companies are already prioritizing current skills over historical credentials. The market already penalizes obsolescence more harshly than ever.

The professionals who will thrive won't necessarily be the most talented. They'll be the ones who never stop learning.

Your university education gave you a foundation. Continuous learning determines whether that foundation remains relevant.

It's not optional. It's not a luxury for when you have time. It's the difference between directing your career and having your career run you over.


The best way to predict the future is to build it. Start with yours.

This article was originally written in Spanish and translated with the help of AI.

Top comments (0)