4 ms·
>The counterpoint to this is the amount of resumes I've had to read and subsequent interviews I've had to sit on from "seniors" or "principals" that they themse
by vsareto 6y ago
>The counterpoint to this is the amount of resumes I've had to read and subsequent interviews I've had to sit on from "seniors" or "principals" that they themselves haven't gone fully into the weeds on whatever technology they've been practicing for 10+ years. The amount is staggering.
You know this is a risk. If you went deep on something like Silverlight, you'd have just thrown away all that time. And then people will casually dismiss your 10 years away as not being relevant. And now you get to pick a new technology to maybe invest the next 10 years on, risking the same thing happening again. If a product dies, you go back to square one as a junior again on some new technology.
Picking a long-lasting technology is hard. You're predicting the future.
I'm really tired of people who think they have this industry figured out like it's easy to predict what will be around in 10 years so you can make safe choices about what to invest time into.
- matfil 6y agoThere's an argument for valuing ten years of Silverlight experience -- especially if it includes some gnarly projects where the framework isn't really holding your hand that much -- over ten years of flitting between web frameworks but never really getting much beyond implementing the stuff that shows up in the tutorial. I think "going into the weeds" (and not being afraid to do so again, in another context) has some value independently of any specific patterns or tricks that apply to a particular technology.