3 ms·

> If you want to get hired, you need to know the tools in fashion now. I think it's an unfair over-generalization. There are quite a few places that started bu

> If you want to get hired, you need to know the tools in fashion now. I think it's an unfair over-generalization. There are quite a few places that started building their tech a fair number of years ago, and have accumulated quite a legacy that needs to be maintained. They would probably want someone with decent knowledge of those dated technologies. The question is, given the choice, would you, personally, want to work on a legacy system, or would you rather prefer to work with something new and shiny. I think the answer will overwhelmingly be the latter. I personally am sure I would pick new and shiny, because it is generally much more pleasant and satisfying to work with than old technologies.

mschuster91 8y ago
> I personally am sure I would pick new and shiny, because it is generally much more pleasant and satisfying to work with than old technologies. I prefer not to be on the bleeding edge of stuff, especially not in the JS world - got bitten too often by incomplete, missing or flat out wrong official documentation, horrenduous bugs, incompatibilities and sudden breaking changes all over the place. Side note to all shiny tool vendors out there, if you want people to try out your stuff, provide usable documentation and don't force your users to copy-and-paste from StackOverflow...
- azangru 8y ago
  I am struggling to think of something that would be both hyped (therefore, popular, and widely used), and at the same time poorly documented. React has a fantastic documentation, but React is hardly bleeding edge anymore. Webpack used to be bad with documentation, but has dramatically improved in the recent couple of years. Vue is said to have documentation that is on par with React’s. Perhaps for RxJS documentation is still a pain point, but other than that... can't really say I have been burnt by documentation.
  - mschuster91 8y ago
    > Webpack used to be bad with documentation, but has dramatically improved in the recent couple of years. Yeah, webpack was definitely the worst offender I remember. How many days were lost in trying to get it to behave... sigh.

mschuster91 8y ago

> I personally am sure I would pick new and shiny, because it is generally much more pleasant and satisfying to work with than old technologies. I prefer not to be on the bleeding edge of stuff, especially not in the JS world - got bitten too often by incomplete, missing or flat out wrong official documentation, horrenduous bugs, incompatibilities and sudden breaking changes all over the place. Side note to all shiny tool vendors out there, if you want people to try out your stuff, provide usable documentation and don't force your users to copy-and-paste from StackOverflow...

azangru 8y ago
I am struggling to think of something that would be both hyped (therefore, popular, and widely used), and at the same time poorly documented. React has a fantastic documentation, but React is hardly bleeding edge anymore. Webpack used to be bad with documentation, but has dramatically improved in the recent couple of years. Vue is said to have documentation that is on par with React’s. Perhaps for RxJS documentation is still a pain point, but other than that... can't really say I have been burnt by documentation.
- mschuster91 8y ago
  > Webpack used to be bad with documentation, but has dramatically improved in the recent couple of years. Yeah, webpack was definitely the worst offender I remember. How many days were lost in trying to get it to behave... sigh.