Download VSCode, setup your fav terminal, install Chrome, have a decent internet.
- SASS, ES6 (and above)
- Prettier, ESLint (please learn to configure them)
- git (please learn the other commands)
- Webpack (just understand what it is & what it does)
- React, Vue or Svelte (Pick one)
- CSS in JS (Styled-components or emotion)
- Gatsby, Next or Nuxt, Gridsome (dunno about Svelte frameworks) (Please stop using CRA when your web app is meant to be used by the public)
- ZEIT now, Netlify & other static hosting cloud platforms
- Headless CMS like Contentful, Wordpress etc...
- Serverless functions
- PWA, AMP
⚠️ Avoid continuously jumping to hypes, keep coding more than talking
With everything above, you'll become a JAM stack engineer actually and you will able to build scalable web apps without the need to learn anything related to backend development, databases & Devops.
Paying those services costs less than paying a full engineering team.
Top comments (5)
"- Please stop using CRA when your web app is meant to be used by the public" This is actually a false statement. CRA is a great starter and works fine for the 'public', I think you mean the problems of SEO ? well if that's the case, you can actually do server side rendering. Gatsby and Next are packed with ready features but that doesn't mean CRA is not suitable for production.
"Paying those services costs less than paying a full engineering team." This is a good story to be told but it doesn't seem true.
""Paying those services costs less than paying a full engineering team." This is a good story to be told but it doesn't seem true."
I agree with Belhassen for the simple fact that, those roles can be covered by simply being a full stack developer and don't necessarily need to be delegated to other team members. (this greatly depends on the scale of things)
A linux vps server is dirt cheap, write your own backend with expressjs and and learn basic linux for devops. (flightplanjs for fully js based continuos deployment)
I find it extra peculiar that this post is tagged with #php. #react would have been both more relavant and offered more visibility
okey i will add it