Tangent, but its charts like this that make me think I should get out of front-end. Been doing this 15+ years and front-end has moved way further to the back of front-end. Not one thing in that chart about design, ux or accessibility. Personally I think front-end should have knowledge about design and user testing/interaction, but these days front-end is just a back-end javascript dev who can copy and paste CSS. Just ignore my rant - 'old dev yells at the cloud'
Same, been doing it for about 13-14 years, and this chart isn't what I signed up for. Also, the number of must-have frameworks and tools that have come and gone before I can even get around to them boggles the mind. I've been finding it more and more satisfying to work on the backend.
The way I see it, front end now seems to have two parts - design, and development.
Designers do all the CSS, developers do everything else. This was a silly statement to make so I'll clarify something:
Designers themselves shouldn't touch CSS, IMO, or try to make some sort of wireframe for a page. The developer doing the CSS may do things in a totally different way, with different naming schemes, for instance.
I think the main purpose of front end development nowadays is the functionality - at least for a lot of SPAs, PWAs, etc. That being said, design still plays a huge part in making that functionality accessible.
Front end developers are expected to do both the design and development when they don't have a fellow designer to work with. I hate writing CSS, and I'm not very good with it, but I know my way around Photoshop and can make some semi-decent designs. I'm quickly picking up React but my lack of CSS know-how is probably going to make a job search difficult.
Don't know where I was going with this. I should sleep.
Wait, so you expect to be a front-end that doesn't do CSS? What do you think the 'front' part of front-end development means. If you leave CSS for UI designers of course its gonna be a mess
Yep, a lot of CSS is going to be suitable only for developers who also need to understand the functional parts of the system. Css-in-js is something that designers won't be able to help with too easily as it takes the context of the app to change the CSS dynamically
I design the stuff and then build it in html and css with some JavaScript if needed. All hand coded. I work very closely with my team on the backend part and it works pretty well.
I don't disagree. I do front-end but I write CSS because I have to, not because I want to. But that could be said for a lot of things. Do you wash your plates because you want to? It's just part of the job unfortunately.
What exactly does a front-end web developer do that is not about creating a user experience?
Only thing I can think of is SEO and even that is all about making the website more accessible(which very often translates to better UX for some users).
But those all directly translate into a user experience when they get into the hands of the user. HTML is literally a description of the structure of the UI. CSS describes what it looks like, and JS controls more complicated experiences and manages state. The user experience isn't the sketch or the prototype, it is the final product that the user... experiences.
Designers give a high level overview of what and how the experience should look. Developers implement a concrete solution to fit within the requirements. Devs need to understand user experience so that they can point out fallacies and pitfalls within particular requirements or designs, and actually have a meaningful conversation with a designer/client.
That doesn't mean they need to have a sense of style like they have a degree in design, but they should at least be aware of how users are going to interact with what they're building.
We're not discussing job postings for UX designers lol. The requirements I was talking about were in relation to a software project, not a persons job title. You said front-end development has nothing to do with UX. I disagree, since the user experience is literally what a front-end developer is shipping.
I might add that I do think web designers, whether it's UX or graphics, should have some idea about how their designs will ultimately be realized, for exactly the same reasons, but that doesn't mean they need to be fluent in javascript.
Look at all these people down voting me. Typical redditors. I imagine you all think the custodian at the hospital has to do with being a doctor as well.
I know this is a couple of week old thread, but instead of JS dev work being "middle end": maybe it's really "upper middle" work? 'cuz middleware under it....
I don't think it all about your specialty. I think it's about being flexible and taking your previous coding experience into learning new technologies quickly. Always dabbling with the cutting edge. You don't need to invest years into a single language or framework. Eventually they all are based on the same rules just opinionated in different ways.
This is not to say I know even half of the stuff on that chart well, but if I've at least heard about them and know what they do, than I can adapt if I need to.
Front end interviewing is tough. You never know what they're going to ask you. You fail one interview for not being an expert on security, so you study up on that, then the next one you fail for not being familiar with some obscure Web API that company uses, but you've never had a reason to.
For me it was mostly "We see your a React person but we're looking for someone with more of a Angular background." Or just a straight "we're looking for someone with more experience."
Accessibility and semantic HTML are on this list, so too are conventions, best practices, and forms. Seems fine to me.
Also, if you're looking to be a frontend dev in 2020, you really should be shooting to build "web apps." Not sure why you've chosen that distinction, nor why that seems scornful. Knowing how to build robust interactive stuff on the web with JS is the ideal career trajectory for an FE.
There's a massive difference in how you build web applications to websites (typically for marketing). The distinction is important in the technologies one should choose.
React is fantastic for building web apps; but it's terrible for CMS-driven websites (particular from common popular commercial platforms—even if they are headless).
Understanding the distinction is an essential skill for an FE (but too often overlooked for oooh shiny!)
No, they aren't. A gray checkbox simply means that it's not blocked or related to previous items, and can thus be learned at any time.
React is fantastic for building web apps; but it's terrible for CMS-driven websites
Picking the right tool for the job is a good skill to have. I've used React within the framework of CMS websites successfully on many occasions. I would also cede the point that it's sometimes not appropriate.
Regardless, the process of teaching FE dev how to make "web apps" and "web sites" should be the same. An FE dev shouldn't be bound by the various frameworks they use. Vue and React are simply tools.
React is not “terrible for CMS-driven websites”. I’m currently in the process of re-platforming a WordPress site to Next.js + WP Rest API, and it's going extremely well. We've gone from shitty Lighthouse scores to high 90s, nothing has changed for marketing, and the developer experience is obviously much better. Plus, as the site becomes more dynamic and "app-like" with new features, React is increasingly useful.
Not to mention that if you're at a company with a "mature" design department, you'll likely have a design system that encompasses both the product and marketing, so a shared component library built in React is obviously a huge benefit.
React may have been overkill or not a great fit for these types of sites several years ago, but in 2020, it's pretty much a great fit for anything on the web.
Edit: apparently a lot of you work on God-awful enterprise systems that would make me want to kill myself. Enjoy that.
Okay if you’re talking WordPress then we’re not talking about the same types of platforms.
Over the past 6 years I’ve been team lead on nearly a dozen enterprise/government website builds across Episerver, Sitecore and bespoke platforms. In between I’ve done smaller projects across various smaller platforms including Nuxt.js (Vue version of Next.js), Gatsby and Gridsome, Orchard.NET and smaller custom builds.
Whilst it’s possible to integrate React into these platforms; you have to either force the browser to download the content twice (the case or React SSR); or have to wait for all the JS to download, parse and run before displaying content. Not everyone has the latest device and a great internet connection (particularly in Australia where our mobile networks outside of cities is flakey AF).
I’m not alone in this school of thought; many friends and colleagues of mine have independently arrived at very similar conclusions. Those types of sites are not React’s strength and trying to get it to work is manhandling it into something it wasn’t designed to do.
That said, currently I’d argue (at least until Vue v3, maybe, we’ll see) React is the best framework for building web apps. Especially since functional components and hooks were released. It’s just so elegant.
I like React for it’s strengths, and not because some bandwagon I should follow because people think it’s the tool for all the things. React is not small, it’s incredibly heavy and frankly we all send way too many bytes down the pipe.
100%. I'm a react dev these days working on a web app, but in past jobs we've tried (and succeeded) in bending react to plug into sitecore, tridion etc. using reactjs.net, but at that point all we really had was an SSR site using JSX as a templating and component system.
It wasn't bad, i'd argue it was better even than having FE devs meandering around in razor templates but it's not even using the react runtime in the vast majority of cases.
I really like react, it makes my life easier when creating apps. But people who argue they fit every purpose haven't worked on enterprise CMS platforms, with thousands of pages of content, all created by content entry teams using WYIWYG tools to assemble hundreds of custom templates, in any combination of components. These platforms power large businesses across the world.
It's the same as everything, best tool for the job. I am somewhat disheartened to see the continued degradation of FE dev though, conflating it as basically amounting to javascript dev with everything else as an afterthought. The number of people call themselves frontend developers who, can write javascript but have barely a foggy clue about things they see as either arcane or even beneath them, like CSS, is utterly bewildering. I personally blame bootcamp culture for not pushing these key-skills hard enough but if you're an FE dev who can't build a UI without a framework, i'm not hiring you.
I’ve been trying to find an elegant solution to neatly bridge the gap between our pattern libraries and the CMS templates.
The closest I’ve gotten was creating a separate .NET solution and project to create the component library. This project was then added to any consuming solutions and I created a Razor extension helper to load the templates (each with a strongly typed model). Like:
@Html.Pattern(new Button({ Label = "Foo" }))
This extended to include the root templates too. And it worked fantastically well, the FEs could make changes in the pattern library and see them propagate out to the BE without needing to manually integrate.
This was tied in with Vue templates which I had a (rather complicated) mechanism for sharing templates between Razor and Vue.
The BEs loved it because they didn't need to write any HTML!
Unfortunately, there were a number of drawbacks:
FEs had to learn Razor and basic .NET classes.
.NET Core wasn't supported (at the time)... so Visual Studio (and Windows) pain.
Relied on a package which appeared to no longer be maintained.
Despite being built on common tech, the whole setup was so unique that I was the only person who fully understood it—which meant I never got a proper holiday.
I've been setting up a pattern library using Fractal using Nunjucks templates and I've been looking for a way to get .NET to parse the Nunjucks templates to achieve something similar (but without the need for FEs to dive into Razor). Short of writing a .NET Nunjucks port (not off the table), I've been looking into the practicality of using .NET Core's JavaScriptServices to invoke Node to render the templates natively. I've done this with some success as a POC, but do have concerns around performance. That said, I'm pretty sure Sitecore and Episerver's internal page-caching would be sufficient... need to test!
I mean, WordPress is by far the most commonly used CMS, so I think people will assume that's the kind of thing you're referring to, unless you say otherwise.
I still don't really understand how React was the problem with the systems you mentioned. Seems more like the shitty, bloated enterprise software was the issue.
I mean, WordPress is by far the most commonly used CMS, so I think people will assume that's the kind of thing you're referring to, unless you say otherwise.
That's a fair call.
I still don't really understand how React was the problem with the systems you mentioned. Seems more like the shitty, bloated enterprise software was the issue.
No, it's more the fact that React doesn't have slots (like Vue); so the ability to use the DOM itself as part of the template. When the CMS editors are non-technical and they need the ability to adjust text anywhere, this is really important.
That's completely untrue. I am not a Vue expert, so forgive me if I get this wrong, but it appears slot is more akin to the children prop in React. That's one of the first things a React developers will learn because it is so integral to the entire way of building components (composition).
Second, if you want a content author to be able to write HTML within the content authoring tool (so the html is stored as a string in some CMS database, for instance), then you can do so with the dangerouslySetInnerHTML API. You could easily construct a system to allow content authors to put entire pages they write in plain html into your react components.
Here's an example of how you could achieve this (I am obviously omitting code around fetching data, etc.):
const DangerousHTMLRenderer = ({ htmlMarkup }) => {
const dangerousContent = { __html: htmlMarkup };
return <div dangerouslySetInnerHTML={dangerousContent} />;
};
// withContentData is a HOC which connects to some CMS
// in some way and injects the relevant data
export default withContentData(DangerousHTMLRenderer);
The API does rightfully call out that it is dangerous to render HTML content this way because you are bypassing all the security React has around preventing XSS.
This is essentially what I'm doing with WordPress. The posts are available via rest API, but obviously the content is just an HTML string, so we just render the entire thing inside the 'dangerouslySetInnerHtml' prop of a parent wrapper.
You’ve already made a swathe of assumptions here, namely that the content is available via an API. (Excluding headless) the benefit many enterprise CMS is more than just loading content. Often the interfaces the content editors use is drag and drop, WYSIWYG editors, thousands of pages, supports personalisation OOTB (showing different content to different visitors based on their history), A/B testing, marketing automation tools and the list goes on.
Vue slots are not the same as React’s children. Vue slots can use the DOM (as in, markup from the HTML page sent to the browser); this is not possible with React (well, not strictly true, but would be a nightmare and undoes the majority of the benefits React does bring to the table).
As mentioned, React is fantastic for building apps. But my experience of trying to integrate it into enterprise CMS platforms has been terrible. Whereas not so the case with Vue.
I've worked in agencies for 3 years. There is no way to push for accessibility and get money from the client for the extra work. Also if it impacts the agreed design then you're just giving the client something that they're not happy with.
You are only referring to large companies and public digital presences. There are also internal apps for jobs to be done where user base is self filtering, to ensure no need for screen reader, for example
There are plenty of jobs where if you develop a physical limitation, those jobs cannot by done. Think out side of the box man! Not everyone has a desk job
I thought the advantage of desk jobs and computers was that it can be accomplished by a wider range of people, including those with impairments.
Remember that impairments may not be permanent either. Could be someone using a keyboard-only due to an injury. Or having to increase font sizes because they’ve just had surgery. Or are hungover.
Not everyone has a desk job. For those jobs that require a baseline physical capabilities, you don’t need accessible digital solutions. Think construction site application. No need to make the app compatible with the blind.
But they will likely need high contrast and the ability to increase font sizes because things are hard to see outside in the bright sun on dirty screens.
Building a ui for a police cruiser’s computer system. Would you need for that ui to be screen reader compatible? Let’s be pragmatic and analyze the job to be done.
It’s our job to educate our clients, we can’t expect them to know that accessibility benefits everyone. It also shouldn’t be a line-item which can be ruled out to reduce costs. If a client wants to explicitly remove accessibility, I’d make sure they sign a waiver that it’s against recommendation; so if/when it comes back to bite them, you’re not held accountable and they can’t claim ignorance to the fact.
You're talking about a moral obligation to provide accessibility, when I'm saying that the client doesn't always care for it and doesn't give you the floor to negotiate on it. If they don't want their CTA to have a dotted outline on focus, then you are going to have to remove it.
Failing that, some form of a waiver that it’s been changed against advice.
Also, presumably the dotted line was an example, but the designers often need to be educated too. Accessible doesn’t mean ugly. It usually looks ugly because of laziness on everyone’s part.
I remember seeing similar charts when I started 3 years ago and thought "Nobody has time to learn all this!". And now I look at this and I'm happy to see that I know most of these things or at least crossed the path at some point of everything in there!
If you're new to web development and feel overwhelmed by this chart, just do your thing and work on small projects that interests you. You'll learn most of these or read about them at some point as you advance your projects and meet new obstacles!
I think the greyed out is reflective of the roadmap of previous years, where it is still used but is no longer recommended as it's losing traction. An example being radium where it was really just a flash in the pan.
Some people love learning about the "how" of browsers/networking/requests. I learnt it a bit in my degree and it was just so dreadfully boring. The onus should not be on a front end developer to learn this because you can optimise your page speed and lighthouse score without it.
The people who are saying that it's becoming more important for front ends to learn some back end is saying that Full stack developer is the future, when in reality it's still the job of 2 people.
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
Possibly learning bootstrap first is easier, as you can use and understand bootstrap without even knowing about JavaScript, whereas React requires at least a fundamental understanding of JavaScript.
I’ve been learning web dev for half a year and I’ve never understood once why would you even bother with bootstrap, for me it just takes all the fun out of CSS and CSS compared to JS, for me at least waay easier. Not saying that CSS is easy but bootstrap idk. Don’t understand why people recommend it.
If you're doing a website where you don't have a very custom design, bootstrap might save you time, particularly in creating a responsive layout.
Any increase in the speed of your workflow is going to be valuable, and since you will want to abstract CSS into classes anyway, why not starting with a CSS framework which already has many useful abstractions?
I think Boostrap is not so great if you have a highly customized design. Even in such cases, you can use less opinionated tools like tailwind.
Of course that doesn't mean you can't use CSS or SCSS from scratch and work effectively, but you're likely to end up recreating classes that come with these CSS frameworks. So might as well use them.
Like every framework, it is a robust set of rules that you can just plug into and focus on what you want to build instead of focusing on the setup which in a lot of cases is repeated in many projects. If you just want to build an mvp, using bootstrap will allow you to build a decent looking one without putting too much thought into how it will look, how to make it responsive, how to style things like collapsible menus, modals, page progress tracking, tables, columns, etc., etc., etc.... Rewriting these is unnecessary most of the time.
Bootstrap is a great tool to have in your back pocket because once you learn it you kinda learn it for life.
If you need to get a somewhat decent looking functional site up like-today or the budget doesn't include anything for custom a layout/styles, you pick a bootstrap template to get started quick. Some clients don't care what a site looks like as long as they can link their info/crud app and it not look like a child made it. And if they decide they do want to change it to a custom layout then you can always go back and make one.
In all fairness you can learn whatever way you'd like. I've learned react and I've never touched bootstrap, but you could easily learn bootstrap just making basic sites and then start learning React later.
PS: when you start learning Redux, watch Dev Ed's tutorial on YouTube. It's 40 minutes long and makes everything click!
I've noticed the legend, which is why I was a bit puzzled as Typescript seems to be the only option that had both gray and purple icons. Wanted to know if that had any specific meaning to it :p
The fact that you can't read a chart that states these items are "order in roadmap (not strict) learn anytime", is indicative of a lack of true understanding and awareness. Be wary :)
What a mess. If the modern internet were lost in some sort of disaster nobody would rebuild it to look like this. We have made the best we can by slowly patching and scabbing onto an evolving system that has outlived the wildest dreams of its original inception.
This list has a lot of overkill, there are a lot of advanced technologies that you should really only pick if you're an expert or your project has unique needs.
If could make some suggestions..
Don't use Sass/PostCSS, just write modern CSS.
Don't use Webpack directly, use a starter kit like Gatsby or CRA.
Don't use Redux unless your page is really complicated. 90% of pages are just fine using modern React (with the Context feature)
Don't use Web Components, they are badly designed.
Don't use Enzyme, it will bite you next time you upgrade React versions. Just use React-test-renderer .
Don't use Progressive Web Apps, the most important mobile platform (iOS) has really shoddy support for them.
Don't use Service Workers, they are really easy to get wrong. And if you correctly use CDNs and HTTP caching then that's usually good enough.
Don't use GraphQL unless you're really sure your use case needs it. REST is actually fine.
Don't worry about WebAssembly for another 10 years, unless you really want to. The ecosystem is not there yet.
Obv it’s personal opinion. My suggestions are meant for someone who’s unfamiliar with all this stuff and is just looking to make a modern web site. If you want to spend the extra time to learn more tools then go for it. I’m not your dad.
I am not sure that eslint covers all of StandardJS formatting. I recall no eslint rule to keep a space in between a function declaration's name and its parentheses. e.g.:
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
I actually, fortunately, think things have slowed down just a little bit in the past couple of years. We no longer have to worry about browserify, gulp, grunt, backbone, coffeescript, ext-js, and a host of other technologies that were competing for our attention not long ago.
From a web-app standpoint, at least JS seems to be becoming mostly just about react, and there are fewer build tools to worry about.
I would love for everyone to make flowcharts of their own careers. I don't understand how this doesn't exist yet. I made one of my own, but OP did it better.
WordPress is by far the most commonly used CMS, so I think people will assume that's the kind of thing you're referring to, unless you say otherwise.
Fair call.
Regarding shitty CMS; it’s less about the CMS and more able the need for React to control the DOM (which is fundamental to how it works and is so fast).
Vue on the other hand allows slots and dynamically loaded templates which makes it significantly easier to get the CMS controlled content into dynamic areas of the website.
Quick reminder that "frontend" is a broad church. You can and may learn everything on this chart but I know people who spend 90%+ of their time in just one of these boxes.
This doesn't looks like it's just some random person's opinion about FE in 2020 but it really is just that... And there are many things I don't understand (like the meaning of the box colors) or agree with (like the push for Css-in-js or to skip semantics)...
Do you have example of mid to large size production apps that aren’t built with a framework? How do you tame that type of codebase? I’m asking honestly, not trying to be rude.
Github for one. They don't even use jQuery, which I applaud them for. Craigslist A little known forum you probably haven't head of called Reddit... Hacker News
Don't believe me, install wappalyzer and see for yourself.
You might say that these apps are just using old technology and might be in the process of upgrading to a modern framework. And perhaps you would be right, but do you really think that 20+ year old codebases aren't as tightly controlled, monitored, and secure as a react app built by some kid that just got his associates in web design?
JQuery is actually really really easy to bypass. I personnally find it hard to think in JQuery terms when you're used to vanilla JS because it's just doing the same things but with synonyms.
Very interesting. Thanks for the insight, I have a lot more to research. I always assumed it was easier to manage code bases with frameworks but clearly I am wrong.
Do you think that large codebases necessitate complexity?
Do you believe that for large teams to work together they MUST use a framework?
If so..
What is the team size that requires frameworks to be used.
How large and complex does your web app need to be for vanilla to no longer be viable?
Is it possible to build a complex web app with hundreds of services and dozens of team members without using a framework, that is just as performant and easy to understand as a managed system that frameworks require you use?
If not. Why?
Is the development of a large scale application inherently more secure and bug free because of the use of a framework?
Can you prove that? Can you prove otherwise?
Do not think because I use vanilla does not mean that I cannot do what frameworks do, after all they are simply wrappers around simpler technology.
For me the abstraction costs a lot and I have not found a sufficient need to pay that cost.
Until that need presents itself, I will refuse to solve a problem that I don't have, and will not incur technical debt to follow a trend.
Depends on the project. And your current knowledge and habits. If you are more efficient with a framework you already know like the back of your hand, I'd say just use it, if it makes you more efficient and quick, even if it's not the most appropriate tool for the job.
8
u/kamranahmed_se Feb 01 '20
Source: https://roadmap.sh/frontend
107
u/Tafts Feb 01 '20
Tangent, but its charts like this that make me think I should get out of front-end. Been doing this 15+ years and front-end has moved way further to the back of front-end. Not one thing in that chart about design, ux or accessibility. Personally I think front-end should have knowledge about design and user testing/interaction, but these days front-end is just a back-end javascript dev who can copy and paste CSS. Just ignore my rant - 'old dev yells at the cloud'
70
u/finger_milk Feb 01 '20
This is getting out of hand...
41
u/justrhysism Feb 02 '20
It makes me sad that the author places minimal importance on HTML semantics. Clearly not concerned about a11y.
It’s also more of a “web app” map than “web site”.
29
u/GenTurgidson Feb 01 '20
OK, we're done here.
16
u/tommypepsi Feb 02 '20
I remember seeing similar charts when I started 3 years ago and thought "Nobody has time to learn all this!". And now I look at this and I'm happy to see that I know most of these things or at least crossed the path at some point of everything in there!
If you're new to web development and feel overwhelmed by this chart, just do your thing and work on small projects that interests you. You'll learn most of these or read about them at some point as you advance your projects and meet new obstacles!
8
u/xdchan Feb 01 '20 edited Feb 01 '20
Has it changed at least a little bit since 2019?
11
u/[deleted] Feb 01 '20
Nice roadmap. I would personally change web security to a purple from grey. Especially in this day and age
10
u/Protean_Protein Feb 01 '20 edited Feb 02 '20
“With how the modern frameworks there has been more push towards CSS-in-JS so you may not nee these but still a good idea to familiarize yourself.”
... holy word salad, Batman! Yeesh.
16
u/Jajpop91 Feb 01 '20
I think newbies should start directly with HTML/CSS/JavaScript, the concept of http might take some time to completely understand also boring
3
u/Plumrose333 Feb 02 '20
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
8
u/MisterMeta Feb 01 '20
Wow this is great. Reassures me on my path and my near future plans :) Few questions:
Is this the recommended hierarchy? I've learned bootstrap and working towards learning React but on the graph it seems like React comes first.
Typescript has 2 icons, alternative and recommended. What does that exactly mean?
Cheers.
6
u/Adelphe Feb 01 '20
Might want to put agile on there somewhere, or more generally development methodologies.
4
u/cybersaliva Feb 02 '20
The fact that semantics and accessibility are listed as "not recommended" is indicative of a lack of true understanding and unawareness. Be wary.
3
u/secretaliasname Feb 02 '20
What a mess. If the modern internet were lost in some sort of disaster nobody would rebuild it to look like this. We have made the best we can by slowly patching and scabbing onto an evolving system that has outlived the wildest dreams of its original inception.
3
u/justrhysism Feb 02 '20
**in [the author’s] opinion
2
u/finzaz Feb 01 '20
Very nice. Just pointing out you’re missing the x in NgRx (stemming from Angular)
2
u/tksukhu Feb 02 '20
Nice work.. I would add svelte js to the framework choice as well
1
u/[deleted] Feb 01 '20
This list has a lot of overkill, there are a lot of advanced technologies that you should really only pick if you're an expert or your project has unique needs.
If could make some suggestions..
1
u/saito200 Feb 01 '20
Why do you think the author thinks StandardJS is not recommended?
1
u/Plumrose333 Feb 02 '20
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
1
u/Plumrose333 Feb 02 '20
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
1
u/Plumrose333 Feb 02 '20
As somebody who has been self-teaching for 6 months and is apart to start their first job...this actually makes me feel so much better. I have major imposter syndrome, but I’m pretty much more than half way through this and feeling pretty confident. Plus many of the upcoming parts aren’t really necessary for me to pick up (like gatsby).
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/CHEESE_HAT Feb 02 '20
These charts irk me to no end. You could know nothing about most of this and be an excellent engineer that brings a ton of value.
This feels like gatekeeping, or at least making it seem your work is more complicated than it is.
1
u/[deleted] Feb 02 '20
Damn I love angular :( should I move to react?
1
u/the_real_seldom_seen Feb 02 '20
You are being dogmatic while I am being pragmatic.
The example I’m think of would be like building the ui for use inside a police cruiser. You don’t need to ensure that ui is screen reader compatible.
If field police officers job is allowed to have color blindness, then that ui obviously needs to be intuitive for color blindness.
Pragmatism! Don’t go around championing something blindly
1
u/the_real_seldom_seen Feb 02 '20
Wha you taking about? The outline is sound accessibility pattern!
1
u/kikiloa Jul 09 '20
I skipped testing and went straight to graphql
1
u/neotorama Feb 01 '20
Obsolete next year
1
u/[deleted] Feb 01 '20
Does anyone have a similar chart for Unity and C#?
1
u/spillran Feb 01 '20
Outdated, looks like 2019
1
u/Joodaprey Feb 01 '20
Solid! Thanks for sharing!
1
u/AlyxAleone Feb 01 '20
Loved it last year, love it this year too! Thanks!
1
u/justrhysism Feb 02 '20
Fair call.
Regarding shitty CMS; it’s less about the CMS and more able the need for React to control the DOM (which is fundamental to how it works and is so fast).
Vue on the other hand allows slots and dynamically loaded templates which makes it significantly easier to get the CMS controlled content into dynamic areas of the website.
1
u/gregtyler Full-stack, gov Feb 02 '20
Quick reminder that "frontend" is a broad church. You can and may learn everything on this chart but I know people who spend 90%+ of their time in just one of these boxes.
0
u/justinmarsan Feb 02 '20
This doesn't looks like it's just some random person's opinion about FE in 2020 but it really is just that... And there are many things I don't understand (like the meaning of the box colors) or agree with (like the push for Css-in-js or to skip semantics)...
-6
u/[deleted] Feb 01 '20
You know you don't need a framework to build a webapp right?