Live data from Hacker News

My GF learned to code in 3 months. This is what she came up with.

nukaco.la

21–30 of 113 posts

Re: My GF learned to code in 3 months. This is what she came up with.

#23

I really like the skills section http://nukaco.la/skills.html I wish this was standard practice for resumes, even though it's subjective assessment it's really easy to compare relative strengths and weaknesses, for example it's very easy to see "dabbled in haskell, very proficient in garage band" just by glancing

I typically just list things I've worked with, no matter the experience level. I like to do so because then the interviewer has to ask about them in an interview, where I'd then get a chance to (subtly) showcase my knowledge and enthusiasm.

From my own anecdote: I had an interviewer ask me about something I had listed in my resume (but not related to the job position). It made for good conversation and allowed them insight that they otherwise wouldn't have seen with a straight technical question.

Edit: Hopefully I didn't go off topic with my comment, but I also think the graphic indicator was a clever and very straightforward way of expressing experience level. It just doesn't seem very space efficient if on a paper resume.

Re: My GF learned to code in 3 months. This is what she came up with.

#26

I really like the skills section http://nukaco.la/skills.html I wish this was standard practice for resumes, even though it's subjective assessment it's really easy to compare relative strengths and weaknesses, for example it's very easy to see "dabbled in haskell, very proficient in garage band" just by glancing

I like it, but in 3 months she got 2/5 in rails, 2/5 in javascript and 2/5 in git? I doubt thats even possible...

I've been working with each of those for ~6 years and I'd still only put myself at a 4 and if I was being generous. It's funny the longer you work with something the more you realize how little you understand it. I probably would have put myself at a 2/5 in those categories 5 years ago, but looking back, I'd rate myself at 1/5 instead.

Re: My GF learned to code in 3 months. This is what she came up with.

#29

I really like the skills section http://nukaco.la/skills.html I wish this was standard practice for resumes, even though it's subjective assessment it's really easy to compare relative strengths and weaknesses, for example it's very easy to see "dabbled in haskell, very proficient in garage band" just by glancing

I like it, but in 3 months she got 2/5 in rails, 2/5 in javascript and 2/5 in git? I doubt thats even possible... I've been working with each of those for ~6 years and I'd still only put myself at a 4 and if I was being generous. It's funny the longer you work with something the more you realize how little you understand it. I probably would have put myself at a 2/5 in those categories 5 years ago, but looking back,…

http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

Re: My GF learned to code in 3 months. This is what she came up with.

#30

I really like the skills section http://nukaco.la/skills.html I wish this was standard practice for resumes, even though it's subjective assessment it's really easy to compare relative strengths and weaknesses, for example it's very easy to see "dabbled in haskell, very proficient in garage band" just by glancing

I like it, but in 3 months she got 2/5 in rails, 2/5 in javascript and 2/5 in git? I doubt thats even possible... I've been working with each of those for ~6 years and I'd still only put myself at a 4 and if I was being generous. It's funny the longer you work with something the more you realize how little you understand it. I probably would have put myself at a 2/5 in those categories 5 years ago, but looking back,…

I think you should look at 1-5 or 1-10 scales logarithmically. It doesn't take a whole lot of work to become basically competent in a git or Rails (2/5), but to become an expert (4/5) takes exponentially more work.
Post reply on HN