DEV Community

Medea
Medea

Posted on

4

Skill section or not?

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?

Top comments (10)

Collapse
 
adam_cyclones profile image
Adam Crockett 🌀 •

I had a crack at improving the readability, through small changes to your design.

  • I would not make a huge deal out of your age, change it from 13 to young, its less specific and will not draw judgment and to be honest its safer.
  • You can take your description and run it through ChatGPT to give you a more full description.

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
Image description

Collapse
 
vulcanwm profile image
Medea •

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

Collapse
 
adam_cyclones profile image
Adam Crockett 🌀 •

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.

Thread Thread
 
vulcanwm profile image
Medea •

i've never built computers with Lego so that sounds like a fun experience

Collapse
 
joelbonetr profile image
JoelBonetR 🥇 •

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 😅

Collapse
 
vulcanwm profile image
Medea •

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)

Collapse
 
theaccordance profile image
Joe Mainwaring •

It honestly doesn't matter one way or the other, do what you think is best for your situation.

Collapse
 
vulcanwm profile image
Medea •

sure, thanks

Collapse
 
vulcanwm profile image
Medea •

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

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs