Today to a company interview, feel the interviewer a very good appearance, perhaps my own expression is not very well, the interviewer has been despised me. During the discussion of a problem, I remember reading it in the book, number is a long, double, int, ... And so on the number type of super class, that the great interviewer actually said, Java API does not have this class, said I was at random writing. When I was interviewed and didn't argue with him, I thought I was in the impression that he insisted that I was wrong ... Later the interviewer has been discriminating against me. I went to the big data job interview, to be honest, some companies, they all recognized my spark and Scala level, but in the eyes of this interviewer I became an idiot, but he did not ask me spark problem ah. Eventually the interviewer asked me the difference between Scala trait and Java interface. I said trait and interface almost, but trait can do things interface to be able to do, but interface can do things trait certainly can do, beginners trait when interface with no problem. Then I also gave an example, I myself use trait's own syntax to implement the Java Proxy design mode, but the interviewer a face of disdain, asked me the underlying principle is what. To tell you the truth, here I have seen many times in the Scala in programmer, time too long, at that time just understood but did not tidy down, the expression is not very clear, the result was despised again, but about this I use very skillfully, I write spark of use a lot of.
This interviewer is the worst one I've ever seen, maybe he didn't know number, but he had a computer to catch Baidu to refute me. Second, I think I'm better at Scala than he is, but my own statements are sometimes not clear. Summary down, also blame oneself interview not prepare well.
Number abstract class for Java