I have a portfolio: https://vulcanwm.is-a.dev and I've seen many portfolios with a Skill Set List.
I want to implement that in my own portfolio, with each skill being a different colour. The colour will represent how long Iβve been using the skill for (eg. Green for 3+ years, Blue for 2+ years).
Should I add a skill set to my portfolio, and if I add it should I add the colour system to it too?
Oldest comments (10)
It honestly doesn't matter one way or the other, do what you think is best for your situation.
sure, thanks
I would personally only write about it, years is an ok example, but what happens when you haven't used something for a whole year.
Is it still 3 years of knowledge? Because it wouldn't stuck in my brain.
But one tip I can give is to NEVER use percentages.
For example: I know 75 % CSS. What does this even mean, that I know how to use 75% of all know CSS attributes? I would have so many questions. So with this you're better of writing down specific Frameworks where you have experience with, years it optional but I would advice against it.
Sure I definitely won't use percentages.
I'll add a skills section and just add the skills in an order from most used to least used
I had a crack at improving the readability, through small changes to your design.
A skills section is great, I always got jobs just saying I have 10 years+ experience as a developer blah blah blah not each skill - the reason is, you need to leave some room for conversation, when you get interviewed you have room to talk your way around a particular point.
Amended idea
sure, i'm turning 14 in 2 days anyways, so i'll change it to young.
i was planning on making the about me section a bit longer since i'll probably remove the tech stack after adding skills
Where you live, how long until you can be employed legally, I think itβs fantastic that your designing a portfolio at this age though, when I was your age I was still just playing Lego and building computers.
i've never built computers with Lego so that sounds like a fun experience
After having multiple portfolios through the years (and currently building a new one) I've decided to reduce it to "what do I use on my daily work", "what can I do in regards of my position", and "what I'm open to use", this way I believe recruiters will understand things off that list as excluded.
I'll probably receive shitty offers in some months but nobody could say I didn't tried π
that's a cool way of showing what skills you use!
i'm just adding boxes for each skill type (eg. languages, web frameworks, tooling)