I always thought it was silly too. Even putting years next to the language or framework I think limits your chances in job applications.
I always tell juniors, just list all of the things that you've had experience with. For example CSS, if you've worked with it before, put it in your resume. If a job application specifically asks for CSS Grid, but you have no experience with it, that doesn't mean you should remove CSS from your resume. I trust most developers, that if they've had experience with a language, that they would be able to learn new things in the language even if they are a beginner.
Well I think years are ok to put next to the skill. Experience matters because it can give you more perspective and where some tech has been and where it is going.
I agree with the second part, but there has to be a limit somewhere. I've seen some assembler code back in high school. That doesn't mean I should put it in my CV :)
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.
I always thought it was silly too. Even putting years next to the language or framework I think limits your chances in job applications.
I always tell juniors, just list all of the things that you've had experience with. For example CSS, if you've worked with it before, put it in your resume. If a job application specifically asks for CSS Grid, but you have no experience with it, that doesn't mean you should remove CSS from your resume. I trust most developers, that if they've had experience with a language, that they would be able to learn new things in the language even if they are a beginner.
Well I think years are ok to put next to the skill. Experience matters because it can give you more perspective and where some tech has been and where it is going.
I agree with the second part, but there has to be a limit somewhere. I've seen some assembler code back in high school. That doesn't mean I should put it in my CV :)