6 ms·

It was said million time here. But if you don't like trying new stuff, learn one stack and stick to it. Nobody is forcing you to try new stuff and then talk abo

It was said million time here. But if you don't like trying new stuff, learn one stack and stick to it. Nobody is forcing you to try new stuff and then talk about js fatigue. Personally I'm exact opposite, I love where js is headed and like all the new stuff and stacks coming. No fatigue at all for me.

austenallred 9y ago
> Nobody is forcing you to try new stuff Well, except for employers
- eloisant 9y ago
  It's usually the developers who push for a switch to the next shiny thing, employers just want a project done in the time and budget.
  - TeMPOraL 9y ago
    The flipside is that they hire expensive professionals and then don't trust their judgement - instead forcing them to use inadequate tooling for the problem. Also related to some enterprise companies selling software solutions to management instead of tech people.
    - deleted 9y ago
      [deleted]
  - BigJono 9y ago
    Quite often the decision to use new tech is made by CTOs, tech leads and senior devs. The majority of jobs are for plain old "one part of a team" dev roles. If you don't have the experience to jump into a role that commands respect, and the industry is trending towards tools that are overengineered or unsuitable for the problem at hand, then it's perfectly possible to find yourself in a position where you either learn how to do the job poorly or find yourself unemployed.
  - adrianN 9y ago
    Unless someone high up has seen a powerpoint with the newest buzzwords and tells the dev department to get on the bandwagon.
  - threatofrain 9y ago
    Business people are often targets for advertising a technological change. In fact, I think big-contract software firms don't target engineers as priorities for advertising, but rather aim straight for business folks.
- Vinnl 9y ago
  If my employer wants to pay me for spending time learning that stuff (and making newbie mistakes in their code), then I guess I can live with that. If they don't and still expect me to follow whatever their whim of the day is, then I'm glad I'm in an industry where I can safely say I'd need to look for another job then.
satyanash 9y ago
in TFA fatigue appears exactly once. The author isn't even the victim of said fatigue. It's just a fancy title.
- tempodox 9y ago
  > It's just a fancy title. AKA clickbait.
BigJono 9y ago
> Nobody is forcing you to try new stuff and then talk about js fatigue This is just not true. I recently had a discussion at work where I was flat out asked "how do you expect to learn new things if you don't try new libraries?". Coming up with a solution yourself (assuming these libraries are even introduced to solve an existing problem, which is sadly not always true) was not seen as an acceptable answer... The options appear to be assimilate into this culture, or find a new industry to call home. Front-end dev doesn't appear to be for people that care more about a lean, pragmatic stack than a trendy one.
- aaron-lebo 9y ago
  Coming up with your own solution when it isn't informed by other solutions just means you are building another poor alternative. Frankly these frameworks and libraries are all very similar and they do very similar things. Once you've learned one you can transition to the others quickly (it's the same way with old web frameworks, MVC frameworks are all the same with minor tweaks). They are worth evaluating though because some of them do one thing better than others, might as well borrow it where possible. I love learning new technology because even if I don't end up using framework x or y, I can pick up the best parts and use it in my own work which becomes simpler and more expressive as a result. I don't want to keep building websites from 2005. There have been some real advances and it's fun touse the best parts.
  - BigJono 9y ago
    Yes, you're building a poor alternative. But you learn far more than you ever would just by using the existing libraries, by virtue of learning what not to do. Using other's tools is trading off knowledge for development time. It's often a good trade to make, but to pretend that learning the API surface of library #34341 is going to improve your skills more is wrong.
    - amackera 9y ago
      Nobody said learning API surfaces is the right way. Most of these frameworks offer fairly simple APIs that are frankly pretty trivial to learn --- the key is to learn the application architecture and why it's different than the alternatives. Anyway, I think we can agree that exposure to other people's thoughts, and also coming up with your own thoughts, is probably the most fruitful way to learn.
bl4ckj4ck 9y ago
Same here. We should remember that JavaScript is a language and React/Angular/Vue are just frameworks/libraries. The latter come and go, the former stays. Sometimes I just think that for JavaScript developers is simply difficult to choose, so someone created the "JavaScript fatigue". Even Java has a lot of frameworks and libraries to choose from, but I don't see any fatigue there. Probably we should just be less open to temporary fashions.
coldtea 9y ago
>It was said million time here. But if you don't like trying new stuff, learn one stack and stick to it. Nobody is forcing you to try new stuff and then talk about js fatigue. You'd be surprised -- since even single stacks change all the time. Try using React Router and keeping it stable. Heck, even React changes paradigms (from mixins and factories, to ES6 classes and pure components, to fibers, etc). And from pure React, to coming up with Flux, 4-6 flux alternatives, the Redux dominating, etc. And let's not get started with things like Angular to Angular 2 et al...
- finchisko 9y ago
  I would not be. React Router 4 is awesome. Wish I had time to write down why. But if you have reason not to upgrade, you can stay on version 3, which is still supported. Same with Angular. Of course there will be examples you're right, but not those two. ;-)
shusson 9y ago
> Nobody is forcing you to try new stuff and then talk about js fatigue. If you read the conclusion, the author is actually very positive about the entire experience.

austenallred 9y ago

> Nobody is forcing you to try new stuff Well, except for employers

eloisant 9y ago
It's usually the developers who push for a switch to the next shiny thing, employers just want a project done in the time and budget.
- TeMPOraL 9y ago
  The flipside is that they hire expensive professionals and then don't trust their judgement - instead forcing them to use inadequate tooling for the problem. Also related to some enterprise companies selling software solutions to management instead of tech people.
  - deleted 9y ago
    [deleted]
- BigJono 9y ago
  Quite often the decision to use new tech is made by CTOs, tech leads and senior devs. The majority of jobs are for plain old "one part of a team" dev roles. If you don't have the experience to jump into a role that commands respect, and the industry is trending towards tools that are overengineered or unsuitable for the problem at hand, then it's perfectly possible to find yourself in a position where you either learn how to do the job poorly or find yourself unemployed.
- adrianN 9y ago
  Unless someone high up has seen a powerpoint with the newest buzzwords and tells the dev department to get on the bandwagon.
- threatofrain 9y ago
  Business people are often targets for advertising a technological change. In fact, I think big-contract software firms don't target engineers as priorities for advertising, but rather aim straight for business folks.
Vinnl 9y ago
If my employer wants to pay me for spending time learning that stuff (and making newbie mistakes in their code), then I guess I can live with that. If they don't and still expect me to follow whatever their whim of the day is, then I'm glad I'm in an industry where I can safely say I'd need to look for another job then.

satyanash 9y ago

in TFA fatigue appears exactly once. The author isn't even the victim of said fatigue. It's just a fancy title.

tempodox 9y ago
> It's just a fancy title. AKA clickbait.

BigJono 9y ago

> Nobody is forcing you to try new stuff and then talk about js fatigue This is just not true. I recently had a discussion at work where I was flat out asked "how do you expect to learn new things if you don't try new libraries?". Coming up with a solution yourself (assuming these libraries are even introduced to solve an existing problem, which is sadly not always true) was not seen as an acceptable answer... The options appear to be assimilate into this culture, or find a new industry to call home. Front-end dev doesn't appear to be for people that care more about a lean, pragmatic stack than a trendy one.

aaron-lebo 9y ago
Coming up with your own solution when it isn't informed by other solutions just means you are building another poor alternative. Frankly these frameworks and libraries are all very similar and they do very similar things. Once you've learned one you can transition to the others quickly (it's the same way with old web frameworks, MVC frameworks are all the same with minor tweaks). They are worth evaluating though because some of them do one thing better than others, might as well borrow it where possible. I love learning new technology because even if I don't end up using framework x or y, I can pick up the best parts and use it in my own work which becomes simpler and more expressive as a result. I don't want to keep building websites from 2005. There have been some real advances and it's fun touse the best parts.
- BigJono 9y ago
  Yes, you're building a poor alternative. But you learn far more than you ever would just by using the existing libraries, by virtue of learning what not to do. Using other's tools is trading off knowledge for development time. It's often a good trade to make, but to pretend that learning the API surface of library #34341 is going to improve your skills more is wrong.
  - amackera 9y ago
    Nobody said learning API surfaces is the right way. Most of these frameworks offer fairly simple APIs that are frankly pretty trivial to learn --- the key is to learn the application architecture and why it's different than the alternatives. Anyway, I think we can agree that exposure to other people's thoughts, and also coming up with your own thoughts, is probably the most fruitful way to learn.

bl4ckj4ck 9y ago

Same here. We should remember that JavaScript is a language and React/Angular/Vue are just frameworks/libraries. The latter come and go, the former stays. Sometimes I just think that for JavaScript developers is simply difficult to choose, so someone created the "JavaScript fatigue". Even Java has a lot of frameworks and libraries to choose from, but I don't see any fatigue there. Probably we should just be less open to temporary fashions.

coldtea 9y ago

>It was said million time here. But if you don't like trying new stuff, learn one stack and stick to it. Nobody is forcing you to try new stuff and then talk about js fatigue. You'd be surprised -- since even single stacks change all the time. Try using React Router and keeping it stable. Heck, even React changes paradigms (from mixins and factories, to ES6 classes and pure components, to fibers, etc). And from pure React, to coming up with Flux, 4-6 flux alternatives, the Redux dominating, etc. And let's not get started with things like Angular to Angular 2 et al...

finchisko 9y ago
I would not be. React Router 4 is awesome. Wish I had time to write down why. But if you have reason not to upgrade, you can stay on version 3, which is still supported. Same with Angular. Of course there will be examples you're right, but not those two. ;-)

shusson 9y ago

> Nobody is forcing you to try new stuff and then talk about js fatigue. If you read the conclusion, the author is actually very positive about the entire experience.