3 ms·

This is skewed a lot by webdev shop stats, where average tenure never exceeds the prime time of an average JS framework.

by varjag 5y ago

Cthulhu_ 5y ago
While this is true - there's a lot of "magpie developers" out there that will jump ship before they have to live with the consequences of their own technology decisions - there's other factors at play as well, like changes in management (because they too want to move up the ladder) or corporate reorganizations. I once worked for a company - a big bank - that during a three year stint did three reorganizations, forcing every team to work as scrum, then in devops teams. They forced the 'old timers', people in their fifties and sixties who had been working there for all their life, to learn Java and to reapply for a job. And for the project I worked on, the original was built in Flex but that didn't work on the new ipads at the time. We rebuilt it in Backbone, then Angular came out and we slowly transitioned to that one - that took nearly two years all told. Then some new CTO came around, an ex-googler so of course his words weighed more heavily, who Decided everything should be rebuilt in Polymer. Of course, right when they were almost finished with making their existing Polymer components work with v2, they introduced v3 and lit-html and everything was Different again. Gee, switching to experimental software has Issues, who would've thought? But it's proven technology because McDonalds used it in their menu screens. Sigh. Anyway, that's the kinda thing that will make people walk out as well.
- tibbydudeza 5y ago
  Reminds me of the eternal sage of the Duke Nukem follow up. First their own 3D engine - then a version of the Doom engine which they needed to "improve" - then Unreal - then by the time the game was close to done Unreal shipped a major upgrade which they needed to "upgrade" to.
tibbydudeza 5y ago
So have you heard of JQuery Plus ???.

This is skewed a lot by webdev shop stats, where average tenure never exceeds the prime time of an average JS framework.

by varjag 5y ago

This is skewed a lot by webdev shop stats, where average tenure never exceeds the prime time of an average JS framework.

Cthulhu_ 5y ago

While this is true - there's a lot of "magpie developers" out there that will jump ship before they have to live with the consequences of their own technology decisions - there's other factors at play as well, like changes in management (because they too want to move up the ladder) or corporate reorganizations. I once worked for a company - a big bank - that during a three year stint did three reorganizations, forcing every team to work as scrum, then in devops teams. They forced the 'old timers', people in their fifties and sixties who had been working there for all their life, to learn Java and to reapply for a job. And for the project I worked on, the original was built in Flex but that didn't work on the new ipads at the time. We rebuilt it in Backbone, then Angular came out and we slowly transitioned to that one - that took nearly two years all told. Then some new CTO came around, an ex-googler so of course his words weighed more heavily, who Decided everything should be rebuilt in Polymer. Of course, right when they were almost finished with making their existing Polymer components work with v2, they introduced v3 and lit-html and everything was Different again. Gee, switching to experimental software has Issues, who would've thought? But it's proven technology because McDonalds used it in their menu screens. Sigh. Anyway, that's the kinda thing that will make people walk out as well.

tibbydudeza 5y ago
Reminds me of the eternal sage of the Duke Nukem follow up. First their own 3D engine - then a version of the Doom engine which they needed to "improve" - then Unreal - then by the time the game was close to done Unreal shipped a major upgrade which they needed to "upgrade" to.

tibbydudeza 5y ago

So have you heard of JQuery Plus ???.