4 ms·

My dislike of dynamically typed languages went through the roof reading through this article.

• slowmovintarget 11y ago
  Your dislike for an interview question that tests knowledge of number theory instead of programming is what should have increased. Writing Clojure functions under pressure is like gardening at 55 MPH. You're trying to make something still and beautiful and overdoing it (or missing entirely) as you drive by.
  • zak_mc_kracken 11y ago
    My point is that most of the runtime errors that the OP had to suffer through would have been caught at compile time with a statically typed language (STL). No interviewer will ever ding you for writing code that doesn't quite compile yet, because it's just part of the process of writing code in an STL. However, with a DTL, every time you run your program and it crashes, the interviewer mentally takes away points. Which is not really fair since it's how DTL's work, but it's a reality: a runtime crash is much more damning than a program that doesn't compile. Stepping back, I think the simple fact that the company this person went to interview with recently switched from Ruby to Clojure would have already been a huge red flag to me.
  • zak_mc_kracken 11y ago
    > Your dislike for an interview question that tests knowledge of number theory "Number theory" is a bit exaggerated. This is a warm up question to see if the candidate is able to decompose number 530 into digits five, three and zero. If you can't do this in a few minutes, you're probably out of the running from the get go.