Ask HN: Does putting Haskell and Common Lisp in my resume a good idea?
I'm an 3rd year CS undergraduate, and I have some projects in Haskell and Lisp (also in Java)
PS: I've worked through HTDP, SICP and PAIP.
PS: I've worked through HTDP, SICP and PAIP.
9 comments
[ 3.9 ms ] story [ 42.5 ms ] threadJust don’t put anything on your resume that youdon’t know well enough to discuss in depth in an interview and start deciphering legacy code in your first day on the job.
I.e. I learned haskell at college, but I never put it in my CV. I have clojure in there, because I actually worked on a small clojure project (while doing QA at RedHat). I did put C++ on my CV, even though I only used it when writing my thesis, because I considered the project large enough. And I did put a sys-admin on there, despite the fact that the work I did with my friends to maintain a community server (I think we had like a forum and a church website there?) was not paid.
In general, I am trying to avoid blank statements like listing an alphabet soup of technologies, and just list various projects I have been part of, scope of my involvement and the technologies I used there. I am not sure if this helps me (mostly been hired through friends), but when I was on the other side, reviewing resumes, I really liked the project-based approach, rather than a list like {java: expert, python: intermediate, haskell: beginner} :D
" -and I have some projects in Haskell and Lisp (also in Java)"
generally a salient approach, such as I have examined what you do here and i believe i have "these skills" that would be valuable to you.
"and i also have these other skills that may or may not be of use but im letting you know, for the point of transparency"