Most of the examples you mention here a very frontend heavy so I wouldn't really call them "full-stack". The closest they get to something related to the backend is using GraphQL.
The projects themselves are great, but they focus on frontend. For a "full-stack" developer to really showcase their abilities, you would need to add at the very least one project that is either backend heavy, or just a full backend project. You need to showcase you can design a good API, that you can handle data being stored, retrieved, etc. That usually includes creating an efficient data model, the relationships between the different models, efficient storage mechanisms, and proper SQL usage.
A quick example could be to create a URL shortener. It can offer a WebUI and an API endpoint to shorten a URL. Make sure that the addresses are stored properly, making sure uniqueness is respected, and that it can handle collisions. Try to use both PostgreSQL and MongoDB as storage backends.
Projects like that should definitely be part of a full-stack developer's portfolio.
Also lets not throw away your skills to deploy your application, it can be either a VM or a bare metal server or a docker image.
Yeah it depends on how it is viewed by each individual, for me Full-stack is Full stack does not matter which tech stack you use, as far as you know how to build and deploy your application.
That's my take as well, yes if you work for a google or AWS this is hardly a full-stack but for some companies this is way over a full-stack, al depends and let's give people a starting point.
Hey patricio,
Thanks for your comment and valid point
I guess there is a big vague area about full-stack.
On papper some of these would qualify, seeing a frontender could connect his frontend too a serverless solution and call it full stack.
I totally get your point,
Would be a great topic too investegate when we can call it full-stack.
I had an interesting talk this afternoon.
The statement was itβs more
product developer
platform engineer
Where a full stack would be a product dev, doesnt really matter what solutions as long as it serves the product
A platform engineer would be someone actually using propper databases and design a solid system.
I found this statement very powerful and maybe more true than using the term full stack.
What would you say?
Nevertheless yes these are easier beginner front end with simple database solution projects.
Still good for people who want to start their journeys as full stack devs
I found this post very helpful. Though I have some side projects of my own it's always good to find new challenges to improve skills. It would be nice to have a follow-up post that focuses more on the back-end part of projects to have a well-rounded full-stack skill set. Thanks!
Most of the examples you mention here a very frontend heavy so I wouldn't really call them "full-stack". The closest they get to something related to the backend is using GraphQL.
The projects themselves are great, but they focus on frontend. For a "full-stack" developer to really showcase their abilities, you would need to add at the very least one project that is either backend heavy, or just a full backend project. You need to showcase you can design a good API, that you can handle data being stored, retrieved, etc. That usually includes creating an efficient data model, the relationships between the different models, efficient storage mechanisms, and proper SQL usage.
A quick example could be to create a URL shortener. It can offer a WebUI and an API endpoint to shorten a URL. Make sure that the addresses are stored properly, making sure uniqueness is respected, and that it can handle collisions. Try to use both PostgreSQL and MongoDB as storage backends.
Projects like that should definitely be part of a full-stack developer's portfolio.
Also lets not throw away your skills to deploy your application, it can be either a VM or a bare metal server or a docker image.
Yeah it depends on how it is viewed by each individual, for me Full-stack is Full stack does not matter which tech stack you use, as far as you know how to build and deploy your application.
That's my take as well, yes if you work for a google or AWS this is hardly a full-stack but for some companies this is way over a full-stack, al depends and let's give people a starting point.
Hey patricio,
Thanks for your comment and valid point
I guess there is a big vague area about full-stack.
On papper some of these would qualify, seeing a frontender could connect his frontend too a serverless solution and call it full stack.
I totally get your point,
Would be a great topic too investegate when we can call it full-stack.
I had an interesting talk this afternoon.
The statement was itβs more
Where a full stack would be a product dev, doesnt really matter what solutions as long as it serves the product
A platform engineer would be someone actually using propper databases and design a solid system.
I found this statement very powerful and maybe more true than using the term full stack.
What would you say?
Nevertheless yes these are easier beginner front end with simple database solution projects.
Still good for people who want to start their journeys as full stack devs
I found this post very helpful. Though I have some side projects of my own it's always good to find new challenges to improve skills. It would be nice to have a follow-up post that focuses more on the back-end part of projects to have a well-rounded full-stack skill set. Thanks!
Can do, but might be a big mix of back-end systems.
So 1 php, 1 node, 1 react, 1 python etc to keep it fair, but really good idea!
Have a look at the below articles for developing full-stack applications with both front-end and back-end
This is the best best idea list I have seen yet! tysm!
I'm glad you found it helpful. Thank you π
Thank you! That's a cool comment to receive.
I love all your articles Chris... keep up the great work!
Wow, thank you so much!
Glad you're loving my articles, will definitely keep it up, closing down on 300 already π
Thank you! This is what i'm looking for.
Glad you found it helpful :)
Nice ones
Thank you!
Great! Thanks for sharing.. Going to start building this to add to my resumeππ
Nice. Thank you π
Nice, I will take a look at those projects.
Thank you
Glad you found them useful