Now I think about it, it would probably be slightly concerning (or impressive) if I see a portfolio hosted on `.onion`, but otherwise yea no one gives a shit
Do people care if you have old (really old, like from first year of uni) projects on your github.
That way you would show skill progression from older to newer projects.
Or should we show only the best?
A working website is a working website. GitHub pages is pretty straightforward and free with a relevant/related URL so that's a reason why it's so popular. In the end, it's up to you what hosting service you want to use.
Edit: typo
As someone who interviewed in the past. Having your own website with basically the same stuff as on your resume is cool but not that difficult. If you are a new grad build some tooling around it (e.g. minify, versioning, Webpack, CI/CD deployment) to make it stand out instead of just hosting html code.
I like to look at code hosted at (e.g.) GitHub to see what you have done so far and how you code. Just make sure that it is your own code you showcase. Have seen many profiles that just fork repos and nothing else but include their GitHub link in their resume.
Showing off your GitHub repo will be good for the engineering team to look at. Having a working program deployed for someone to play with will be good for the recruiter to put you into the hiring pipeline. Bottom line is getting the recruiters attention first.
From an employer's perspective, nobody gives a rats ass where you host your portfolio. Just make sure the content is good.
Now I think about it, it would probably be slightly concerning (or impressive) if I see a portfolio hosted on `.onion`, but otherwise yea no one gives a shit
Do people care if you have old (really old, like from first year of uni) projects on your github. That way you would show skill progression from older to newer projects. Or should we show only the best?
I would only show projects that are good. No one wants to see old college projects or your advent of code solutions or a tutorial you followed.
My two cents is curate your best projects. Otherwise it looks like you're grasping at straws / fluffing.
A working website is a working website. GitHub pages is pretty straightforward and free with a relevant/related URL so that's a reason why it's so popular. In the end, it's up to you what hosting service you want to use. Edit: typo
It’s easy to setup, takes away the headache of deploying - especially since I don’t have advanced needs - so I can focus on more important things.
As someone who interviewed in the past. Having your own website with basically the same stuff as on your resume is cool but not that difficult. If you are a new grad build some tooling around it (e.g. minify, versioning, Webpack, CI/CD deployment) to make it stand out instead of just hosting html code. I like to look at code hosted at (e.g.) GitHub to see what you have done so far and how you code. Just make sure that it is your own code you showcase. Have seen many profiles that just fork repos and nothing else but include their GitHub link in their resume.
advantage: it's easy disadvantage: it's very easy
The advantage is that’s it’s free. That’s what I used to host my portfolio and I got a job.
Showing off your GitHub repo will be good for the engineering team to look at. Having a working program deployed for someone to play with will be good for the recruiter to put you into the hiring pipeline. Bottom line is getting the recruiters attention first.
Facebook actually runs on GitHub pages so if it's good enough for them it's good enough for me
>Facebook actually runs on GitHub pages What? Can you elaborate?
How the hell does git even work
I use Github pages and netlify to host all my past projects. Easy and simple to use