What should I be learning after React.js and Node.js?
There are lot of technologies which are emerging and it's very confusing what to learn and what to leave, I want to learn stuff which will make be a better full stack engineer. I have a year experience building full stack applications and I want to improve my toolkit for better jobs (as in the job description on freelance websites they mention so many things). Can someone who followed this path already suggest me what to do next? Should I learn docker or what? please give me details. Thank you in advance!
Posted Mar 7, 2020, 12:30 PM UTC
15
If you want to stick with web development then learn databases, data modelling, SQL. Learn about storage, backup and recovery. That'll keep you busy for a while and it's absolutely essential as a full-stack developer.
On top of that, yes, containers can be very helpful. I deploy to Kubernetes (managed on Digital Ocean) and have found it to solve a lot of my packaging and deployment problems I had in the past and it forces me to think about horizontal scaling and resiliency from the beginning. Containers can also be great for development.
Devops, infrastructure.. those are also very important for full-stack. That means monitoring, logging, service maintenance, security, system architecture, cloud services such as AWS.. loads of stuff.
You'll be busy for the next 10 years. If you just want a job then don't even think about it in terms of full-stack; learn some popular frameworks (Django, Laravel, Spring, Rails, .NET) and apply for related positions. Not many employers expect to find genuine full-stack developers. You're already employable with React and Node, you could hone those skills, maybe expand into TypeScript. You can't learn everything.
Thanks for the great response. Yes database stuff I really need to understand. How did you start learning about containers, does that mean learning docker and Aws? Lmao I don't want to learn so much right now.
Welcome to software. Your career will involve constant learning :P one of the most challenging aspects is managing your limited time and energy and deciding what to learn and what to pass.
Containers means learning Docker, that's all. It can be great for development alone because you can quickly fire up different dependent services for your application, and you can pull down all kinds of packaged 3rd party services without configuration headaches. Docker compose, for example, allows you specify multiple services in a single config file and run `docker-compose up` to start the services, `docker-compose down` to stop them.
Deploying containers is a bit of a step forward because then you need to think about how you're going to maintain running containers in a production environment, how you'll monitor and log them, restart them, etc. What many started to do was use 'container orchestrators' which is what Docker Swarm and Kubernetes are. AWS has a service called Elastic Beanstalk which uses containers (probably others, I'm not that experienced with AWS) and Google has Google App Engine for containers.
But definitely give Docker a go locally and don't worry yourself too much about deploying containers as yet. Use whatever method you currently use and explore that later if/when you get time.
Hey it's okay for learning. The stuff you said which will take me 10 years to learn, I mean I don't want to learn all of that. Containers and Docker stuff seems awesome to me and I look forward to learning it. If I am able to write docker files for node.js and react.js apps and able to deploy them, is that a good move for now?
That's a great move! You'll learn a lot in the process.