For me, showing that you're familiar with general concepts is better than specific software. If you have extra space, write "version control", don't write "svn"

For me, showing that you're familiar with general concepts is better than specific software. If you have extra space, write "version control", don't write "svn". If you don't have the space, don't bother. If your interview doesn't make me confident that you can and will learn the basics in an afternoon, no hire. Only list languages that you're comfortable being interviewed in. If I see a language on your resume, I may ask you to whiteboard a solution using that language. If you can't, I'm going to wonder where else you stretched the truth. Be prepared to describe at least one project per language listed. Thus, don't list languages you haven't written cool projects in. Make sure your cool projects are front and center, by the way. You worked for company X? Great. What cool things did you do there? You write open source software in your free time? Awesome. You created an interactive website related to a hobby you're passionate about? We don't do websites, but that's still way cooler than the kid who worked at an internship all summer and can't tell me one interesting thing he did there. The best resume advice I can give you is this: I look at your resume for maybe fifteen seconds at a career fair or thirty seconds if I'm sitting at my desk. Make a list of everything you want on your resume. Sort it by most to least epic. Make sure everything on the "most" end stands out. Make it easy for me to find information about you (grade level/professional experience level, type of job sought (intern/full time), graduation date/date you're available for hire) so that I have more time to look at your epic stuff. Any employer who's going to be impressed because you have vim or MS Office on your resume is not one I would want to work for; if you feel the same, don't even bother listing it.