Show HN: Web Skills – A Visual Learning Guide for Web Developers
andreasbm.github.io
Show HN: Web Skills – A Visual Learning Guide for Web Developers
1–10 of 24 posts
Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#2Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#3Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#4Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#5Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#6Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#7Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#8Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#9Re: Show HN: Web Skills – A Visual Learning Guide for Web Developers
#10I would not include any mention of build tools or bundlers. These are subjective developer tools not aligned to any standard and not in any way benefiting the user or the user experience. This is true of the Framework section below as well, but more so.
I get the feeling many front end developers cannot imagine any web application that is not a basic service driven SPA built on a major MVC framework. When people complain about reinventing the wheel they are complaining about the need to innovate because their framework does everything for them and that is the only type of application to build in the browser.
If you are going to provide large blocks of content on build tools and frameworks you should also provide content on services, Node, Deno, protocols, messaging, and so forth.