4 ms·
When I hire I look for specific types of knowledge, not specific languages (even Lisp and Smalltalk, which are still on my resume). IMO it's really difficult to
by davelnewton 10y ago
When I hire I look for specific types of knowledge, not specific languages (even Lisp and Smalltalk, which are still on my resume). IMO it's really difficult to tell how much, or what, people know, by looking at standard resumes.
Just putting Clojure on a resume is meaningless--I can put anything I want on a resume. It's meaningless until you talk to the person and find out if they have the basic concepts of multiple paradigms down.
That said: having "interesting" tech on a resume means at least they know the words and they might be more likely to have a strong developer mind.
- bryanlarsen 10y agoAgreed, from the perspective of an interviewer. But from the perspective of a student, putting down 'Lisp' is probably better than putting down 'functional programming'. The former implies the latter, but either way the interviewer is going to have to verify. And from the perspective of telling a student what to learn, saying "learn functional programming" isn't as actionable as "learn Lisp".
- thepredestrian 10y agoI did a variation of Lisp (called Racket) in for my first CS course in college. Since you recommend getting good at it (or at least being competent enough to demonstrate that in interviews), any tips on how once with a very basic foundation of functional programming can proceed?