If those projects from Frontendmentor and Udemy were inside of the course. Meaning that the teacher created them and you just followed what they did and recreated it. Then it does not count as your own project and I would most definitely not put that on your resume. Because it is like plagiarism it's not your codebase all you did was copy and paste.
Yes I would add the retail and finance degree because you need to show them some experience that can relate to the role you are applying for. Retail experience could mean you are a people person and know how to communicate well. And the finance means you must be good with numbers which is obviously good for a programmer.
I'm not sure how much experience you have but it might be a good idea to wait until you have a fairly strong portfolio before you apply for junior roles. Because they will compare you half completed broken projects against applicants that have fully working production ready apps and you could get overlooked.
"I'm not sure how much experience you have but it might be a good idea to wait until you have a fairly strong portfolio before you apply for junior roles. Because they will compare you half completed broken projects against applicants that have fully working production ready apps and you could get overlooked."
OMG, yes you have a huge point there. That's why I am still practicing my development skills. I know the competition is fierce even for junior developers. On my portfolio I have my two best projects so far. Every other project is on Github. And of course I'll be working on more.
And as far as Udemy and Frontendmentor projects, I am fully aware about not claiming course projects as my own. But, as far as Frontendmentor goes, they give you the images and guidelines to work with but you have to use your OWN code to design the website. So I rather put that on my portfolio. Even on their website they say it's okay to add their projects to your portfolio.
Thank you so much for replying. This has made me reconsider a lot of things.
Be clever. You want to have a simple site - treat it as a CV, show your skills. Make the programming as clean as possible, my aproach was a very simple white site where I demonstrated my text design skills. That also showed I understood SCSS, critical CSS and treeshaking, ETC.
This is the problem. People are all learning the same material. New ideas are coming out but they are the same ones we batttled with a decade ago just with much larger packets.
I suggest learning deno if you use node and show that. Go white with one secondary color. Make several versions on github sites.
There are so many things that are oldschool and people appreciate because they show understanding rather than the modern - use everybody else's automation.
Make sure to program your CSS youself, but use the preprocesssor of your choice.
Learn the history because as a junior you are likely to be updating a site. Don't think you are a fullstack programmer because you use react and MVC. Take a day to learn Ruby fundamentals and see if it interests you - what's your end goal. AI? UX, SEO, Data scienece? there are a million "fullstack react devs" who have been told that client side rendering is a good thing and to follow the money because that pays their mentors. Be focussed, start simple, and decide what direction you want to focus on.
I hope this helps a bit, if you want me to expand on any point ask away.
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.
If those projects from Frontendmentor and Udemy were inside of the course. Meaning that the teacher created them and you just followed what they did and recreated it. Then it does not count as your own project and I would most definitely not put that on your resume. Because it is like plagiarism it's not your codebase all you did was copy and paste.
Yes I would add the retail and finance degree because you need to show them some experience that can relate to the role you are applying for. Retail experience could mean you are a people person and know how to communicate well. And the finance means you must be good with numbers which is obviously good for a programmer.
I'm not sure how much experience you have but it might be a good idea to wait until you have a fairly strong portfolio before you apply for junior roles. Because they will compare you half completed broken projects against applicants that have fully working production ready apps and you could get overlooked.
"I'm not sure how much experience you have but it might be a good idea to wait until you have a fairly strong portfolio before you apply for junior roles. Because they will compare you half completed broken projects against applicants that have fully working production ready apps and you could get overlooked."
OMG, yes you have a huge point there. That's why I am still practicing my development skills. I know the competition is fierce even for junior developers. On my portfolio I have my two best projects so far. Every other project is on Github. And of course I'll be working on more.
And as far as Udemy and Frontendmentor projects, I am fully aware about not claiming course projects as my own. But, as far as Frontendmentor goes, they give you the images and guidelines to work with but you have to use your OWN code to design the website. So I rather put that on my portfolio. Even on their website they say it's okay to add their projects to your portfolio.
Thank you so much for replying. This has made me reconsider a lot of things.
Be clever. You want to have a simple site - treat it as a CV, show your skills. Make the programming as clean as possible, my aproach was a very simple white site where I demonstrated my text design skills. That also showed I understood SCSS, critical CSS and treeshaking, ETC.
This is the problem. People are all learning the same material. New ideas are coming out but they are the same ones we batttled with a decade ago just with much larger packets.
I suggest learning deno if you use node and show that. Go white with one secondary color. Make several versions on github sites.
There are so many things that are oldschool and people appreciate because they show understanding rather than the modern - use everybody else's automation.
Make sure to program your CSS youself, but use the preprocesssor of your choice.
Learn the history because as a junior you are likely to be updating a site. Don't think you are a fullstack programmer because you use react and MVC. Take a day to learn Ruby fundamentals and see if it interests you - what's your end goal. AI? UX, SEO, Data scienece? there are a million "fullstack react devs" who have been told that client side rendering is a good thing and to follow the money because that pays their mentors. Be focussed, start simple, and decide what direction you want to focus on.
I hope this helps a bit, if you want me to expand on any point ask away.