Roadmap to becoming a React developer in 2018
1–10 of 153 posts
Re: Roadmap to becoming a React developer in 2018
#2I'm always fascinated by these -- it puts hard earned skills (that I would otherwise take for granted) in perspective. Thanks!
A few suggestions: I would argue that Redux isn't required (but suggested), and instead a Flux implementation is required.
I would also argue that SASS (or LESS) preprocessor experience isn't required but also just suggested.
Re: Roadmap to becoming a React developer in 2018
#3I'm always fascinated by these -- it puts hard earned skills (that I would otherwise take for granted) in perspective. Thanks! A few suggestions: I would argue that Redux isn't required (but suggested), and instead a Flux implementation is required. I would also argue that SASS (or LESS) preprocessor experience isn't required but also just suggested.
I've been using plain css for my React stuff so far but I do miss a lot of the syntactic sugar Sass allows, like nested selectors, BEM extrapolation, colour utilities etc. What is the norm for people these days when it comes to CSS and React? is css-in-js very popular at all?
Re: Roadmap to becoming a React developer in 2018
#4I'm always fascinated by these -- it puts hard earned skills (that I would otherwise take for granted) in perspective. Thanks! A few suggestions: I would argue that Redux isn't required (but suggested), and instead a Flux implementation is required. I would also argue that SASS (or LESS) preprocessor experience isn't required but also just suggested.
I've been using plain css for my React stuff so far but I do miss a lot of the syntactic sugar Sass allows, like nested selectors, BEM extrapolation, colour utilities etc. What is the norm for people these days when it comes to CSS and React? is css-in-js very popular at all?
PostCSS is probably the standard. Many plugins to get all the same stuff as sass, but faster and cleaner.
Re: Roadmap to becoming a React developer in 2018
#5I'm always fascinated by these -- it puts hard earned skills (that I would otherwise take for granted) in perspective. Thanks! A few suggestions: I would argue that Redux isn't required (but suggested), and instead a Flux implementation is required. I would also argue that SASS (or LESS) preprocessor experience isn't required but also just suggested.
I've been using plain css for my React stuff so far but I do miss a lot of the syntactic sugar Sass allows, like nested selectors, BEM extrapolation, colour utilities etc. What is the norm for people these days when it comes to CSS and React? is css-in-js very popular at all?
Styled-components has been a godsend, especially in apps that I'm working on with others.
You really don't need nested selectors in most cases, since you're rarely thinking about the page context when dealing with a single react component.
Styled components does namespacing for you and it's easy to share styles, colors, etc. across components for reusability (a la mix-ins) and portability via the props abstraction.
Re: Roadmap to becoming a React developer in 2018
#6I wonder why "General Development Skills" comes after basic HTML/CSS/JS. I guess the barrier-to-entry feels lower if you dive right in, but it feels odd that extremely basic things like "Learn to search for solutions" would proceed HTML. Wouldn't you need to be good at that in order to help you learn even basic HTML when you get stuck?
Re: Roadmap to becoming a React developer in 2018
#7I'm not a react dev per se, I've used it some, not a 'master', I prefer Vue, but I wanted to chime in for newbie devs, take this roadmap with a grain of salt, you don't need to be an expert at using all the tooling and all topics mentioned in this diagram to get started and build stuff.
A topical understanding of each thing will suffice, then dive in deeper as you need it for whatever project you're working on.
If you're between projects on your job, or between clients if freelancing - by all means pick a weak subject and level up on, but don't let the complexity get you discouraged from learning in the first place.
Re: Roadmap to becoming a React developer in 2018
#8I wonder why "General Development Skills" comes after basic HTML/CSS/JS. I guess the barrier-to-entry feels lower if you dive right in, but it feels odd that extremely basic things like "Learn to search for solutions" would proceed HTML. Wouldn't you need to be good at that in order to help you learn even basic HTML when you get stuck?
If you look at the career trajectory of frontend developers, I'd bet that more of them learned HTML, CSS or JS before they learned many (if not all) of the things listed under "General Development Skills". Not that those skills aren't important, but they're not entry points for learning.
Re: Roadmap to becoming a React developer in 2018
#9[deleted]
Re: Roadmap to becoming a React developer in 2018
#10Earlier quoted context omitted.
I've been using plain css for my React stuff so far but I do miss a lot of the syntactic sugar Sass allows, like nested selectors, BEM extrapolation, colour utilities etc. What is the norm for people these days when it comes to CSS and React? is css-in-js very popular at all?
Styled-components has been a godsend, especially in apps that I'm working on with others. You really don't need nested selectors in most cases, since you're rarely thinking about the page context when dealing with a single react component. Styled components does namespacing for you and it's easy to share styles, colors, etc. across components for reusability (a la mix-ins) and portability via the props abstraction.
I'm going to echo styled-components being a godsend.
I've built a ton of front-end applications, both pre- and post-react. I've tried a ton of implementations of CSS, including just using PostCSS. After all my time investigating the best way to approach CSS, I think style-components is the best solution to use with React.