From my own experience a DON’T that I always recommend is “don’t use progress bars nor percentages against your list of skills.” For example:
JavaScript - 95%
HTML - 99%
CSS - 99%
TypeScript - 90%
Figma - 80%
This is problematic because the values are too subjective. Does the above mean you know 99% of the CSS spec (even the draft spec) by rote? How do you measure that 5% difference between JS and TS? And how do you compare 80% “skill” in a design tool (Figma) against “skill” in a scripting language (JS)?
In my experience, it’s better to just list the skills and then show (rather than tell) your skill through your well developed and designed portfolio site and accompanying body of work.
Software Team Lead at Intechnica and Netacea. Founder at: 📈 sentimatic.io, 🧠 aitheory.io, ⚖️ stealth #legaltech. Writing about programming, product, startups.
I was trying to make portfolio(retro-style) website for the first time, and I did typing animation because that seemed good for me and also I added the progress bars for the skills section. So yeah I did almost everything you said not to do
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
A fraction is just another way of writing a percentage (or a progress bar):
3/5 = 60% = ▓▓▓▓▓▓░░░░
In my experience, you are better off listing JavaScript skills you are proficient in, and then providing examples of work that reflect those skills.
For example, you might highlight your skills with async/await and interacting with REST APIs. You could show this by including a project that demonstrates your understanding, such as a static blog that generates its pages from the dev.to API.
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.
Really great article and solid advice. 👌
From my own experience a DON’T that I always recommend is “don’t use progress bars nor percentages against your list of skills.” For example:
This is problematic because the values are too subjective. Does the above mean you know 99% of the CSS spec (even the draft spec) by rote? How do you measure that 5% difference between JS and TS? And how do you compare 80% “skill” in a design tool (Figma) against “skill” in a scripting language (JS)?
In my experience, it’s better to just list the skills and then show (rather than tell) your skill through your well developed and designed portfolio site and accompanying body of work.
Yes. And why would you downplay yourself?
Well said, I totally agree!
Came to say this!
Also please no more typewriter animation
I was trying to make portfolio(retro-style) website for the first time, and I did typing animation because that seemed good for me and also I added the progress bars for the skills section. So yeah I did almost everything you said not to do
Hey!
It was trendy a couple of years ago, I know I need to redo my portfolio but this isn't gonna happen anytime soon, stop reminding me about it 😂😂😂
What about rating skills out of 5?
For example Javascript 3/5
A fraction is just another way of writing a percentage (or a progress bar):
3/5 = 60% = ▓▓▓▓▓▓░░░░
In my experience, you are better off listing JavaScript skills you are proficient in, and then providing examples of work that reflect those skills.
For example, you might highlight your skills with async/await and interacting with REST APIs. You could show this by including a project that demonstrates your understanding, such as a static blog that generates its pages from the dev.to API.