DEV Community

Discussion on: What's the best career decision you've ever made?

Collapse
 
virg1l profile image
Virgil

Let me provide a counter-argument to 1, because so many people love it: if you specialize, you narrow down your options. So, you're the world's most renowned expert in MUMPS? Congratulations, but almost everybody stopped using it and there are a total of 10 companies you can work for in the entire country, only one in your city. Hope it doesn't go under, or you don't get into a conflict with you boss.
Best Symbian developer in the country? Sorry, Nokia almost went bankrupt, and switched to Windows anyway. What, you thought that'd never happen?

The narrower your specialization field, the more at risk you are that the entire field will be disrupted, and the less jobs are available to you. Better hope that you picked your specialization well! And remember, we all suck at predicting the future. Yes, even you.

Collapse
 
jermdavis profile image
Jeremy Davis

Interesting point - but I'd argue that being a specialist shouldn't mean tying yourself to one technology forever.

I've been working in web content management for sixteen years now, and am on my fourth major CMS. I (and the company I work for) have "specialised" in all of them for a while, but we've been flexible enough to jump ship to different technology when we see one system getting overtaken or when our market's needs change.

I'd also make an argument that demonstrating that "ability to adapt and learn new stuff" skill is a really good thing for your CV alongside "really knowledgeable about something". IT changes fast, and good employers should value people who can understand and adapt their skills to those changes.