@kburr | kburr.io
Instead of having a plain list like the above, how do you list your skill set / differentiate your understanding & experience with them?
I've been using the above setup for awhile, but I have a couple of problems with it:
1) The list can get long, and potentially lose its value. Does ordering matter?
2) What do I include? What shouldn't I include? At what level of understanding, does a specific skill warrant inclusion?
3) I'd like to differentiate my exposure to each (ex, I'd consider my Rails a 7/10, but my JavaScript a 6/10), potentially ranking by understanding or months/years.
4) What about languages / frameworks that I have used in side projects and/or am just picking up? I'd like to include them because it shows that I'm interested in picking up new stuff, but their inclusion with what I would consider my core skill set might backfire if it is assumed those skills are all equally developed.
feedback from devs or hr people would be amazing.
Similarly, how many hours after sending an email do you assume it has been read? 2 hours? 4 hours? 12 hours? a day? Do you assume that an email you sent in the morning of a weekday will absolutely have been read by the end of that night? And whatever time range you expect an email to have been read, what is your expectations for a response?