5 ms·
I’m currently organizing a roadmap for improving my full-stack skills. I work in JS with Node and React. Does anyone have any opinion on whether I should spend
by nefitty 6y ago
I’m currently organizing a roadmap for improving my full-stack skills. I work in JS with Node and React.
Does anyone have any opinion on whether I should spend time learning Deno and Typescript instead of digging deeper into what I already know? I find it hard to tell if Deno will start showing up in job descriptions in a few years, or if Node is so entrenched that it would only distract me from building on my current skills.
- albertgoeswoof 6y agoTypescript will completely change your productivity and is a massive game changer for JS. You don’t even have to learn much for it to add massive value.
- franklyt 6y agoI’m a huge fan, but I also think that merely leveraging type checking with jsdoc is powerful. It also keeps me more honest because I’m not going through the trouble of typing a parameter or variable just to make it any.
- mywittyname 6y agoAny good resource recommendations.
- pdevr 6y agoYoutube videos: 1. Clément Mihailescu has a good summary done in less than fifteen minutes. 2. FreeCodeCamp.org has a long video.
- albertgoeswoof 6y agohttps://github.com/bitjson/typescript-starter https://github.com/bitjson/typescript-starter
- throw_m239339 6y agoDefinitely learn Typescript type annotations/compilation pipeline.
- brendanmc6 6y agoMaster typescript and you will be rewarded greatly! It is a fantastic tool with a very high level of adoption already. It makes React significantly easier to write and refactor. You won’t ever go back to plain .js! Deno is not relevant enough, I would wager 99.99% of the existing projects you might find yourself working on in the next few years will be using node somewhere in the stack. It shouldn’t be hard to pick up deno when it eventually does show up.
- nicoburns 6y agoYes, this. Use TypeScript with Node and/or React.
- bavell 6y agoAgreed, TS is a big productivity boost and is here to stay, definitely worth investing time into if you want to get further into JS ecosystem. You can safely ignore Deno for the time being.
- gutino 6y agoNow is possible to use many NPM packages in Deno, find out on the Web
- christiansakai 6y agoDeno is still incompatible with JS ecosystem
- gutino 6y agoNow is possible to use many NPM packages in Deno, find out on the Web
- christiansakai 6y agoInteresting, I didn't know that. What's the catch?
- Soremwar 6y agoThe catch is that it works in a case by case basis. The most used libraries are there and work wonders, but things like the Vue compiler won't work with NPM transformations and are better off with a native port, like VNO
- capableweb 6y agoIf you only ever worked in JS (browser and/or server), branch out. Try different things instead, it'll make you a better JS developer (and better developer in general) if you try to learn things that are far out from your current skill set. If you're into types, go for Haskell or Erlang. If you're into dynamic runtimes, go for Clojure or Smalltalk.
- franklyt 6y agoGreat advice, but I think going for a more mainstream alternative would be a bit more suitable career-wise.
- qudat 6y agoI'm not sure there's much to learn with Deno. It's typescript with a different import syntax, package management, and a different standard library. Learn how to use Typescript, it's pervasive in the JS ecosystem and very easy to learn now.
- blockwood 6y agoThese developer roadmaps might be helpful :) https://roadmap.sh/ https://roadmap.sh/