Once your daily practice is under control, the next horizon is longer: how do you stay relevant over a career that will outlast several generations of the technology you’re using right now.
The article explain that the principle career rule isn’t the one you expected.
-
Thirty Years in Infrastructure ICT Taught Me One Career Rule. It Isn’t the One You Expect.
I was twenty-four when a man twice my age handed me a folder and said: “If this network stops, trains stop.” I laughed. He didn’t. That was the last time I found the sentence funny. Everything I’ve learned about surviving a career happened in the thirty years after it. Here’s the part nobody warns you…
Why this matters
Every generic career article ends with “keep learning, stay current.” This one, written from three decades in infrastructure projects, argues that it’s not actually the rule that keeps people employed once their equipment, protocols, and vendors have become obsolete.
If your entire professional value depends on knowing how today’s technology works, you have an expiry date. This article names what doesn’t expire.
Expected outcomes
After reading, you should be able to separate, in your own career, what is “technical knowledge with an expiry date” from what is “experience that compounds,” and describe one thing you do that would still be valuable if the specific technology you work on disappeared tomorrow.
Self-check
If the platform or tool I’m known for became obsolete next year, what would still be true about my value at work? Am I the person people come to because I know a tool, or because of how I think through problems? When did I last update my skills versus update my judgment?
Best practices
Keep a short, running list of decisions you’ve made that turned out right — and why, in your own reasoning, not the tool involved. That list is your actual portfolio of transferable value, and it’s worth more than most certifications.
Remediation
If your professional identity is currently built entirely around one tool, platform, or certification: pick one piece of judgment you’ve developed around it — a way you evaluate risk, a way you scope a project, a way you spot a bad requirement — and practice explaining it without naming the tool at all. If you can’t, that’s the gap to close next.
Further reading
A shorter, direct companion on the same theme.
-
I Didn’t Choose Digital Transformation. It Arrived Where I Was Already Standing.
People ask me why I work in digital transformation, and the honest answer is uncomfortable. I didn’t pick it. When I started, the phrase didn’t exist. There was no category, no conference track, no consultancy practice with that name on the door. There were networks that had to stay up, and there was me, twenty-something,…
Leave a Reply