3 ms·
And let's say that they found their "dream" candidate that knew GWT. Technologies change and improve over time, can you imagine a place that is still using GWT,
by ralphc 2y ago
And let's say that they found their "dream" candidate that knew GWT. Technologies change and improve over time, can you imagine a place that is still using GWT, or jQuery, or backbone? Whoever they hire is going to have to learn new technologies while working there, otherwise they need to fire all their devs and go back out and hire React devs or whatever is the flavor of the day.
Even something as stable as Java has changed dramatically as it has absorbed functional and parallel concepts from Scala and Kotlin. Any dev should be hired on their ability to learn, not, or not just, on what specific tech they know now.
- pdimitar 2y agoIt was not about GWT at all. That was exactly my point: passing on a senior just because they don't know $specific_tech that can be learned in 2 weeks is a short-sighted business decision.
- shagie 2y ago> ... otherwise they need to fire all their devs and go back out and hire React devs or whatever is the flavor of the day. One of the companies in the area has a strict N year cycle for contractors. After N years all contracts end and they rehire for the next cycle. If the technology stack changes then they hire different contractors as the projects forecast needs. I am not saying that this is a good idea - lots of domain knowledge gets lost ever N years... but it is a solution the "we can't require contractors to learn new skills and are unable to hire for the aptitude to learn new things."