I personally do not care much if the person I interview knows about such or such latest api. Rejecting a person because he/she gets stuck on a technical question is no relevant. You have to look at learning, abstraction, adaptation, communication abilities. You have probably already rejected great potential contributors.
Hiring someone just because of a particular technical knowledge is asking for troubles. Once I had a developer who knew Java much better than anybody else in the team. The problem is that he could not understand where we wanted to go because he was just looking at the technology. His contributions ended up being less than the not-so-skilled java developers. Another time I gave the chance to a young guy out of high school. He knew about nothing about programming languages but he strucked me as a problem solver. After one month in the team he knew more that the senior developers about the project and even if he did not know about the lastest tech issues, he solved the different problems you have in daily IT work in a more efficient manner. Finally, even though I use JSP, I have the tendency of building frameworks asap to focus on real business issues. I will probably fail your tests although I built a framework on top of Tomcat to help my web developer focus on the customer issues. Of course, if you are trying to build technology such as a JSP and/or a J2EE, you do need deeper tech knowledge. Still I will argue that solving problems is more important than narrow tech knowledge. Thierry -----Original Message----- From: Ruben Gamez [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 3:34 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer Like I said, I'm not looking for a specific answer - just give me a smart answer! -----Original Message----- From: Hart, Justin [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 5:31 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer I heartilly disagree. You posted to a mailing list specifically about this topic, and got 5 different answers. -----Original Message----- From: Ruben Gamez [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 5:24 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer I don't want a programmer that wouldn't know that. If you've spent ANY amount of time writing Servlets, you SHOULD know doGet and doPost. That is very basic. -----Original Message----- From: Hart, Justin [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 5:21 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer It's not that it's difficult, but I wouldn't ask questions about specific functions/parameters/methods. I have written plenty of java, and couldn't tell you what methods most specific interfaces implement. I couldn't even tell you what methods the interfaces that I've written implement. Instead, I would look for conceptual knowledge. I think that just about anybody can spit up wrote knowledge like that after an hour of studying and not know how to implement a thing, but most people who understand the actual concepts couldn't tell you what methods or how many methods, or what their parameters are. Just my $.02. -----Original Message----- From: Ruben Gamez [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 5:17 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer Does anyone else think that what I'm asking for is so difficult? -----Original Message----- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 4:54 PM To: Tomcat Users List Subject: RE: Java/JSP/Servlet Programmer On Fri, October 17, 2003 at 1:27 pm, Ruben Gamez sent the following > The first is a written test which has J2SE, Servlet, and JSP questions. > The second is a programming test, they must write a JSP page that form > posts to a Servlet, that retrieves ANYTHING from a Bean and outputs it > in the Servlet. I have a lab computer set up with everything except the > code. They must also use notepad to do this. Wow, sounds like entry level coding to me! And you're having trouble getting people to pass these things? -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
