So generally, I find these questions select for “how well do you understand how artificial interview questions work?” rather than “how well do you understand the programming language”.

Of course, the compiles could optimize an Integer into an int if that is needed, but to a developer there should be no difference.

I totallt agree that NullPointerException shoud not be thrown when auto-unboxing fails… AutoUnboxingException (which, fo course, inherits from NullPointerExeption) is much better.

I must say that the more I use Java, the more I dislike Java as a language. On the other hand, the more I use Java, the more I like Java a platform (the JVM, and all the available tools, etc).

Think so too. We two talked about the DefaultServlet question some years ago, but I forgot. Might be good to try :-)

It still remains a somewhat low-level entry point for a high level discussion. I usually prefer a top down discussion, while your question indicates a bottom up approach to me. (I might be wrong, though).

So nowadays I start a second interview with a larger piece of code (such as the famous tomcat DefaultServlet) or a typical non-technical customer requirement. There might be a good chance we end up in a low-level discussion, but it’s up to the applicant whether we talk about requirements, software design and/or low-level implementation details.

It seems my interview strategy (that pretty much reflects our day-to-day business) makes it difficult to talk about low-level issues. And due to our business low-level focus isn’t always a plus.

I think we simply use two different strategies to reach the same goal;).

But beside that getting someone to know how he does error handling - in my opinion - has nothing to do with Java but with design and thinking skills -especially thinking about your co-developers who need to work with your code. So in the end perhaps it’s mostly about social skills.

“[...] importance of communication [...]”

Excactly. But discussing Exception handling with me, and thinking about other developers, is about communication skills. Defending his choice, making concessions, seeing my points is all about communication.

So I cant’ see this as a Java question or “lower level programming skills” but more about thinking skills, communication skills, design skills and social skills.

If I have to choose between someone with basic programming skills who understands the importance of communication and the importance of business requirements OR someone with (very) good programming skills who tends to avoid direct communication with their ‘customers’ and team members I would always choose number one. This is because I believe programming style and programming skills are more or less a team issue. Therefore it can be trained - while missing social skills (and pattern) can’t.

Of course this implies that you have at least one experienced team member who likes to teach and train (and management supports that strategy).

So the unboxing (or better defensive design and programming) question might be a good question for your key (infrastructure) developers. And even in these cases I look for other - more important - skills first. Why? Because I believe even design philosophies depend your existing team members and require good social skills of your key architects/developers.

Disclaimer: I have to deal with typical business applications day by day. Everything I said might not apply for other types of software.