Latest / Career Skills with Fexingo: Hard Skills, Soft Skills, and Future-Proofing Your Career / How Skill Decay Creates Hidden Career Risk
Transcript
- Lucas: So here's a question that doesn't get asked enough: what happens to a skill you stop using? I mean, we all assume it just stays there, ready to be dusted off. But the data suggests otherwise. Luna: You're talking about skill decay. Like, if I haven't used my Spanish in six years, I'm not going to suddenly be fluent on a trip to Madrid. Lucas: Exactly. And research on knowledge retention — there's a famous study from the 1880s, believe it or not, by Hermann Ebbinghaus — shows that without reinforcement, we lose about 50 percent of new information within a few days, and then the forgetting curve levels off. But here's the career-relevant twist: the same applies to procedural skills, like coding or operating machinery. Luna: So it's not just trivia. If I'm a front-end developer and I switch to backend for a year, my React skills start to erode. Lucas: Right. And that's the hidden risk. We talk a lot about learning new things — skill stacking, skill borrowing, all the positive moves. But we rarely audit what we're losing. A study from the military on skill decay found that after 6 months of non-use, performance on complex tasks dropped by 30 to 50 percent. That's not trivial. Luna: That's huge. And it means if you're making a career pivot, you need to have a plan to maintain the old skills you might still need. Lucas: Or you need to accept that you're going to let some skills decay intentionally. That's a strategic choice. But most people don't decide; they just drift. They stop doing something, and then six months later they're rusty and they don't know why. So today I want to talk about how to be deliberate about skill decay: which skills to preserve, which to let go, and how to maintain them efficiently. Luna: Can we start with an example? I think that makes it concrete. Lucas: Sure. Let's take someone in manufacturing who learns to program a robotic arm. If they move into a supervisory role and stop hands-on programming for a year, that skill decays. But if they need to step back in temporarily — say, to troubleshoot a new robot — they might struggle. A study in the Journal of Applied Psychology showed that in manufacturing, skill decay for complex psychomotor tasks hit 30 percent after a year of non-use. Luna: That's a real productivity hit. And it's not like you can just re-learn it instantly. The same study showed re-training takes about half the original learning time. Lucas: So the cost is real. And then in software, it's even more acute because the tech changes. You might not just lose proficiency in a language or framework; you might also miss updates. So your skill decays not only from lack of practice but from obsolescence. That's a double hit. Luna: Right. So how do you prevent it? I mean, you can't do everything all the time. Lucas: No, you can't. And that's the key insight: you have to prioritize. One method is spaced practice. Instead of cramming a skill refresh once a year, you spend 15 minutes a week on it. That's enough to flatten the forgetting curve. Ebbinghaus himself found that spaced repetition dramatically improves retention. Luna: So for the React developer who's now doing backend, that means maybe one small React ticket a sprint. Or a Friday afternoon coding challenge. Lucas: Exactly. Another approach is peer review. Even if you're not actively coding in a language, reviewing someone else's code keeps your pattern recognition sharp. You can identify issues, understand new idioms, and maintain a baseline of fluency without writing much code yourself. Luna: That's smart. And it's a low-effort way to stay in the loop. I've also seen people use teaching — like, hosting a lunch and learn or writing a blog post — to force themselves to articulate a skill. That reinforces it. Lucas: Teaching is actually one of the most effective retention strategies. There's a concept called the 'retention rate' from the Learning Pyramid: teaching others yields a 90 percent retention rate, compared to 5 percent for lecture. So if you care about a skill, teach it to someone — even a colleague who's not an expert. Luna: But what about skills you do want to let go? How do you decide? Lucas: That's a harder question. I think you need to ask yourself: what is the probability that I'll need this skill in the next 2 years? And if it's low, and the cost of re-learning it is manageable, then it's okay to let it decay. But if re-learning would take months — and the skill is still relevant to your career — then you should invest in maintenance. Luna: So it's a cost-benefit analysis. And the cost of maintenance might be lower than you think. Fifteen minutes a week is nothing. Lucas: Exactly. And that's the practical takeaway. Instead of feeling guilty about skills you've lost, be intentional about which ones you keep. Do a skill inventory — maybe once a quarter — and identify two or three core skills that are at risk. Then set a tiny maintenance habit. Luna: I want to try that. I think I'll list my top five skills and rate my current proficiency and how often I use them. Then pick one to maintain. Lucas: That's a great exercise. And if you do it, you'll probably find that some skills have decayed more than you realized. That's okay — the first step is awareness. Luna: You know, I think this episode is really useful for anyone who's made a career switch or is thinking about one. Because it's easy to assume your old skills are still there, but they might not be. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It's a small way to keep the show independent and focused on practical advice. Luna: Yeah, no ads, no sponsors, just us digging into topics like this. So if you got something out of it, that link is buy me a coffee dot com slash fexingo. Lucas: And we'll keep making episodes that help you think about your career differently. So back to skill decay: the key is to be deliberate, not passive. Know what you're losing and why. Luna: Alright, I'm going to do that quarterly check-in. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.