4 ms·

Maybe you need less engineers trained in the new hotness but just experience with, uh, older hotness. Which may be easier to find.

marcinzm 7y ago
Engineers want what is best for them and not what is best for the company. That is the right choice for them. New hotness is one way to entice them. Far, far from the only one but it is a tool in the CTO's tool belt.
- eeZah7Ux 7y ago
  > New hotness is one way to entice them. Only the bad ones.
- TeMPOraL 7y ago
  Then consider this: a startup in its job ad is probably simultaneously talking about the hottest new tech and passion for building a reliable product. But the intersection between these two is vanishingly small. So what kind of hires do you want to optimize for? CV-driven developers, or people who know how to build reliable and efficient software fast?
- kabdib 7y ago
  This is why you need to be interviewing for things like "customer focus" as well as the technical side of things. I've rejected candidates who have been great on their technical skills . . . who I would never want to be making ANY decisions about customers, or the technical direction of the company.
- karatestomp 7y ago
  Developers will stop caring about having experience in the latest hot thing when that stops being very important in interviews. I hope, but doubt, that will happen before I'm retired or have been ageism'd into something else.
- alexbanks 7y ago
  I feel like for any company, there should probably be a balance between old a new. If all of the technology from 10 years ago was inarguably "the best", I don't think we'd be in the situation we're in now. Everything is pros and cons. My team right now, for example, had a mantra of "No JS frameworks, just Rails" which was absolutely dreadful. Rails UI is absolutely dreadful. I can't say enough, it is absolutely dreadful. So we recently made the move to use React for more "dynamic" UIs, which has brought up somewhat of a happy medium? React will be here in 5 years, Rails will be here in 5 years, everyone wins.

marcinzm 7y ago

Engineers want what is best for them and not what is best for the company. That is the right choice for them. New hotness is one way to entice them. Far, far from the only one but it is a tool in the CTO's tool belt.

eeZah7Ux 7y ago
> New hotness is one way to entice them. Only the bad ones.
TeMPOraL 7y ago
Then consider this: a startup in its job ad is probably simultaneously talking about the hottest new tech and passion for building a reliable product. But the intersection between these two is vanishingly small. So what kind of hires do you want to optimize for? CV-driven developers, or people who know how to build reliable and efficient software fast?
kabdib 7y ago
This is why you need to be interviewing for things like "customer focus" as well as the technical side of things. I've rejected candidates who have been great on their technical skills . . . who I would never want to be making ANY decisions about customers, or the technical direction of the company.
karatestomp 7y ago
Developers will stop caring about having experience in the latest hot thing when that stops being very important in interviews. I hope, but doubt, that will happen before I'm retired or have been ageism'd into something else.
alexbanks 7y ago
I feel like for any company, there should probably be a balance between old a new. If all of the technology from 10 years ago was inarguably "the best", I don't think we'd be in the situation we're in now. Everything is pros and cons. My team right now, for example, had a mantra of "No JS frameworks, just Rails" which was absolutely dreadful. Rails UI is absolutely dreadful. I can't say enough, it is absolutely dreadful. So we recently made the move to use React for more "dynamic" UIs, which has brought up somewhat of a happy medium? React will be here in 5 years, Rails will be here in 5 years, everyone wins.