Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
I think there might be some confusion with our definitions here.
"Full Stack" and "Front End" stand at odds with each other.
A "Full Stack" developer is someone who can build both the front end and the back end of an application.
A "Front End" developer is someone who is comfortable building front end applications and (optionally) designing those applications as well.
Front End developers will typically design and implement layouts, implement client APIs, and perform UX/UI performance tuning.
Back End developers will typically work with databases, design and build APIs, implement server-side integrations like payment gateways, and help with systems architecture.
Full Stack developers will do all of the above to some capacity.
True that (this is what happens when you try to post being super tired), what I was actually trying to say was a front end dev who wants to move to full stack. Guess I should reformulate the whole thing.
Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
I'd pick a single stack to start with, and just build solutions using that and covering the above topics. Most of the skills will be pretty easily transferrable between languages and frameworks.
If you're already a front end developer, I'm going to assume you are using js so I'd recommend learning how to build an API with express, hooking it up to a database (don't know if mongodb is still as dominant in the node ecosystem), and as a bonus hosting it on AWS. Honestly, if you're already competent with js you'd be surprised how much you can actually build once you learn what I recommended.
For a more senior level, you'll want to learn more about architecture and security, so maybe add some authentication/authorization to your API and potentially look at splitting it into microservices.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think there might be some confusion with our definitions here.
"Full Stack" and "Front End" stand at odds with each other.
A "Full Stack" developer is someone who can build both the front end and the back end of an application.
A "Front End" developer is someone who is comfortable building front end applications and (optionally) designing those applications as well.
Front End developers will typically design and implement layouts, implement client APIs, and perform UX/UI performance tuning.
Back End developers will typically work with databases, design and build APIs, implement server-side integrations like payment gateways, and help with systems architecture.
Full Stack developers will do all of the above to some capacity.
Full stack isn't just front and back end. It's also the middleware and infrastructure. It's every part of the stack.
True that (this is what happens when you try to post being super tired), what I was actually trying to say was a front end dev who wants to move to full stack. Guess I should reformulate the whole thing.
No problem!
In that case my suggestion would be:
Theory:
Technologies:
I'd pick a single stack to start with, and just build solutions using that and covering the above topics. Most of the skills will be pretty easily transferrable between languages and frameworks.
Thank you! This is great clarification.
If you're already a front end developer, I'm going to assume you are using js so I'd recommend learning how to build an API with express, hooking it up to a database (don't know if mongodb is still as dominant in the node ecosystem), and as a bonus hosting it on AWS. Honestly, if you're already competent with js you'd be surprised how much you can actually build once you learn what I recommended.
For a more senior level, you'll want to learn more about architecture and security, so maybe add some authentication/authorization to your API and potentially look at splitting it into microservices.