3 ms·

So why not talk about what he's wrong about, instead of writing ad hominem attacks on him?

• cookiecaper 16y ago
  Does everyone have to provide a unique in-depth analysis of the subject before they can make a comment? Maybe the rest of the thread adequately illustrates why advice from a recruiter is not necessarily credible and this comment is just made to tip people off before they get to the bottom of the article. I think that the guy can throw in an off-hand remark without having to provide boons of evidence. I don't see a problem with pointing out that this guy speaks from the outside looking in.
• arethuza 16y ago
  Largely because it regards developers as a commodity that can be summarized with a few keywords - which is something I have always hated. Incidentally, I did co-found a start-up in '94 where we chose Java as the platform because we wanted to to do shrink-wrapped server side applications. Java was probably a lot less popular then than Scala is now and that choice turned out to be a huge advantage for us technically. I don't think any of first round of developers we hired had any real Java experience - it really wasn't a problem.
• sgift 16y ago
  While ad hominem attacks are never good, I don't think this is an ad hominem, but rather an argument based on knowledge/professionalism: A recruiters opinion on programming languages is like the opinion of my baker on medicine: It's nice to hear it, but I don't need a long discussion to decide on their usefulness.