what's used to generate a png of this kind, pretty impressive and better than freemind
Roadmap to becoming a React developer in 2018
31–40 of 153 posts
Re: Roadmap to becoming a React developer in 2018
#32what's used to generate a png of this kind, pretty impressive and better than freemind
https://www.draw.io/
Source was at the bottom of link.
Re: Roadmap to becoming a React developer in 2018
#33Earlier quoted context omitted.
Who cares about face. The best time to learn is when you have to. That's not to say be lazy, it's to say continuously challenge yourself so you frequently "have to".
It's not about face. It's about being able to effectively deliver stuff without needing to blow all estimates because you have to learn everything. My family doctor constantly has to learn about new things, but he needs to have a basic foundation so he doesn't have to learn everything every time a new patient comes in the door. If he did, I'd go see someone else.
[deleted]
Re: Roadmap to becoming a React developer in 2018
#34Earlier quoted context omitted.
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.
styled-components is what got me to switch from LESS to css-in-js, and I'm so grateful. Anyone interested learning about css-in-js for the first time would benefit from understanding the styled-components model, but there's already churn in that category, and new libraries inspired by styled-components that take it further. Here's an interesting perspective on the history of CSS-in-JS: https://github.com/streamich/fr…
5 generations to make something that is less efficient (slow build times, caching not always possible) that straight up css processors. Its kinda sad really (but hey my css is in my js file now, so useful).
Re: Roadmap to becoming a React developer in 2018
#35I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. Learning happens contextually as you figure things out. I see no use to learning half of the things on here that you'll never use. You do risk, however, in the confusing and complex JavaScript landscape, getting paralyzed by choice and never getting off the ground. I shutter thinking about…
This exact ideology hindered me when I first started learning to program. If I had decided to learn Just Enough To Get Crap Done I would've fared much better and joined the industry much sooner.
Thankfully I found a good mentor who helped steer me away from all the terrible specifics and trying to learn the full stack and only learning what I needed
Re: Roadmap to becoming a React developer in 2018
#36Couple of nits & questions: 1) I'm surprised CSS preprocessors made it as a must, and CSS in JS as only recommended. I figured that would be switched, isn't the current golden path CSS in JS? 2) Is webpack a must these days? Can we not just throw everything in typescript? Maybe that's only personal preferences! 3) No one ever needs to know jQuery anymore ;) Glad to see lodash made it though
Babel and TypeScript compete. WebPack is orthogonal.
WebPack can take your PNG image and inline it into base64-data if it's small enough, or return a hashed filename from your import to be cache friendly but without the caching bugs.
Re: Roadmap to becoming a React developer in 2018
#37Couple of nits & questions: 1) I'm surprised CSS preprocessors made it as a must, and CSS in JS as only recommended. I figured that would be switched, isn't the current golden path CSS in JS? 2) Is webpack a must these days? Can we not just throw everything in typescript? Maybe that's only personal preferences! 3) No one ever needs to know jQuery anymore ;) Glad to see lodash made it though
Don't throw away jQuery just yet.
Especially with the way Safari is being developed, I'm guessing we're going to go back to needing a jQuery library to handle all the browser inconsistencies.
Re: Roadmap to becoming a React developer in 2018
#38I'll take Rails + turbolinks over this tangled mess any day.
Re: Roadmap to becoming a React developer in 2018
#39I'll probably get down-voted to oblivion for suggesting this, but is there a C#/.Net developer roadmap? I can only find quite generic front/back end developer roadmaps online.
You might find Pluralsight's "Paths" of value - https://www.pluralsight.com/product/paths
They have a few C# & .Net related paths. They offer free trials as well. Here's a 10 day affiliate link one. Not sure if there are better ones out there. https://pluralsight.pxf.io/c/1197267/424552/7490
Re: Roadmap to becoming a React developer in 2018
#40I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. Learning happens contextually as you figure things out. I see no use to learning half of the things on here that you'll never use. You do risk, however, in the confusing and complex JavaScript landscape, getting paralyzed by choice and never getting off the ground. I shutter thinking about…
> I've noticed this spirit of "learn everything" all over the React and JavaScript community, and I don't think it's a good thing. I strongly disagree there. The only way for an engineer to make good decisions as to what tools / framework to pick from is to know and understand as much tech as possible. It is fundamental for an engineer to do this job of tech-watching in order to not become religious and blinded by th…
Strong disagree to your strong disagree. I understand right tool for the right job, but for the job of"front end framework" React vs Angular isn't hammer vs screwdriver, or even sledge vs ball peen - it's like Dewalt vs Milwaukee, claw hammers both.
For a given class of problem, your comfort with the technology will outweigh the edge cases you hit with one choice vs another. So pick your favorite hammer, screwdriver, saw, and tape-measure. If someone else hands you theirs sure, use it, but the time you spent learning the ins and out of everything is _way_ more than any time you will save.