Originally posted by Simon Lee:
"Name all methods of the Object class"
"Describe what each of the methods do"
"Descibe how you would use/override the methods"
Anybody who calls themselves a Java programmer yet cannot do the above is a fraud.
Sometimes the only way things ever got fixed is because people became uncomfortable.
Originally posted by Simon Lee:
Mark, I think if you were in an interview situation you'd be able to get them all (well apart from registerNatives(), I wouldn't expect anyone to get that (including me).
Originally posted by Tim Holloway:
I can't name all the member functions of class java.lang.object. But I'm aware enough of its functionality to be able to know what to look for in the JavaDocs.
Since I lack an eidetic memory, there's absolutely no way I could claim expertise in as many areas as I do based on sheer rote memorization, but I have been accused of the next best thing, because I usually know exactly where to look it up and how, in minimum time, to apply what I've found there.
I don't feel bad about that. Knowing the class details is knowing where you're coming from. What's more important to me is knowing where I'm going to. The world is changing, and it's part of my ambition to be one of those agents of change - or, in other words, to not limit myself to what was or what is, but to look to what can be.
Originally posted by Simon Lee:
I think the Object class.
I've been asked this in an interview (was Reuters BTW) & think it's a great question;
"Name all methods of the Object class"
"Describe what each of the methods do"
"Descibe how you would use/override the methods"
Anybody who calls themselves a Java programmer yet cannot do the above is a fraud.
You know how to turn the interview process scenario from interviewee to interviewer and watch the adversary scratching his behind or whatever convenience at the time.
Have you thinking about switching interview strategy from technical oriented to business problem solver oriented? Did you have any advanced degree?
Sometimes the only way things ever got fixed is because people became uncomfortable.
Originally posted by Tim Holloway:
the largest university in the state decided it was time to add C to their curricula. :roll:
Originally posted by Matt Cao:
You are kidding! C has been around for very long time after Basic and Fortran, I think. It's just so difficult not many students like it.
C is just so difficult not many students like it.
Originally posted by Matt Cao:
In California, starting from Stanford Univ. all the way down to State Univ. all Engineering and CS freshmen must learn C.
Originally posted by Simon Lee:
I think the Object class.
I've been asked this in an interview (was Reuters BTW) & think it's a great question;
"Name all methods of the Object class"
"Describe what each of the methods do"
"Descibe how you would use/override the methods"
Anybody who calls themselves a Java programmer yet cannot do the above is a fraud.
Sometimes the only way things ever got fixed is because people became uncomfortable.
Simon Lee states:
Since this thread is starting to become one on more general interview questions, I'd say the best interview is when the interviewee manages to turn the tables & drive the interview.
If you get a gift of a question like this, try and use it to take control.
John Coxey
Evansville, Indiana, USA
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
|