I usually only put technologies I have used for work I was paid for, or at least was reasonably public. I.e. I learned haskell at college, but I never put it i

I usually only put technologies I have used for work I was paid for, or at least was reasonably public. 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