Hello, I'm a self-taught developer predominantly writing in Python & Javascript, here to write for beginners behind me, and for feedback from veterans ahead of me! I also love DevOps!
This looks fantastic, and well done on making it portable for any dev to use. I'll definitely recommend this to anyone looking for a quick magic bullet.
I do really like the timeline from the resume JSON, but I will say the skills section with percentages is a trend that's never made much sense to me. Scripting skills are 95% of what? Your overall skill-set? But then Troubleshooting is also 95% so what's the overall value? There is absolutely an importance in demonstrating your proficiency in certain areas, but I don't believe the percentages do the job, just adds confusion.
I did previously have something similar on my site which aggregated from my Github contributions to determine percentages of languages used from all contributions. This is slightly better since there's an absolute value, but even still, it gets skewed (big stylesheet imports can make CSS seem like your top language).
I would say (from my own personal observation, I'm no authority on this topic) that the percentages themselves are often ignored and just an obstacle in the way of reading a skills list. Maybe this could be best converted to a sectioned list of skills with proficiency enumerations like "Beginner, Intermediate, Advanced, Master" similar to LinkedIn?
I wasn't involved with the candidate selection process, but recently I was on an interview panel for a Java role. One candidate's CV listed their skills as percentages. It made no sense. What does 70% Java mean? They know 70% of everything there is to know about Java? Certainly not! So what, then?
I was wondering this same thing. 70% of your projects involve Java? Or, like you say, "they know 70% of everything there is to know about Java?" Unlikely, for sure, and how would you quantify such a thing, whatever the case? Respectfully, it seems like meaningless data.
This looks fantastic, and well done on making it portable for any dev to use. I'll definitely recommend this to anyone looking for a quick magic bullet.
I do really like the timeline from the resume JSON, but I will say the skills section with percentages is a trend that's never made much sense to me. Scripting skills are 95% of what? Your overall skill-set? But then Troubleshooting is also 95% so what's the overall value? There is absolutely an importance in demonstrating your proficiency in certain areas, but I don't believe the percentages do the job, just adds confusion.
I did previously have something similar on my site which aggregated from my Github contributions to determine percentages of languages used from all contributions. This is slightly better since there's an absolute value, but even still, it gets skewed (big stylesheet imports can make CSS seem like your top language).
I would say (from my own personal observation, I'm no authority on this topic) that the percentages themselves are often ignored and just an obstacle in the way of reading a skills list. Maybe this could be best converted to a sectioned list of skills with proficiency enumerations like "Beginner, Intermediate, Advanced, Master" similar to LinkedIn?
I wasn't involved with the candidate selection process, but recently I was on an interview panel for a Java role. One candidate's CV listed their skills as percentages. It made no sense. What does 70% Java mean? They know 70% of everything there is to know about Java? Certainly not! So what, then?
I was wondering this same thing. 70% of your projects involve Java? Or, like you say, "they know 70% of everything there is to know about Java?" Unlikely, for sure, and how would you quantify such a thing, whatever the case? Respectfully, it seems like meaningless data.
I see a lot of people don't like the percentages 😄.
It's definetily something to work on for the next releases.
Thanks a lot for the feedback
When does the next release will be public pro? :D
It isn't that we dislike them, can you tell me, when you say, "Java, 70%", what does that mean to you? What are you saying? Help us understand.