Interview with the interlocutor
I'm not an asp programmer, but since you were asking for opinions, here's one from Joel
Just for fun, here's the worst interview question on Earth: "What's the difference between varchar and varchar2 in Oracle 8i?" This is a terrible question. There is no possible, imaginary relationship between people who know this particular piece of useless little things and people that Fog Creek wants to hire. Who cares, what's the difference? You can find out online in 15 seconds!
a source to share
I would say this is a great interview question.
Active Server Pages (ASP)! = ActiveX Data Objects (ADO)
a source to share
Okay, they might even ask you what they want. About Perl, Python and Ruby, this interview, they can measure your knowledge in other languages (if you've heard of them or know why .NET is better / worse).
In an interview, it is important that you answer the questions to the best of your ability, so my opinion, if you don’t know, then just say what you don’t know about ADO Record Set
, but you will list the benefits / features.NET DataSet
a source to share
The best I've found in an interview if you don't know the answer to something isn't quiet, then try to rekindle it. Be ahead, say that you don't know, but if you had a guess to guess, then it would be appropriate. The interviewer will judge honesty, not everyone knows everything. People want to see confidence, but also humility :-)
a source to share
I would say this is pretty pointless these days. Anyone who doesn't know probably just didn't work with old apps. All ADO functionality has been outdated for about ten years now, and there are many excellent developers with years of experience who have never seen ADO.
I have hired a lot and the difference between really great candidates and average ones is not that it is unclear what they know now, but that they can quickly pick up when they need to.
In short, a really good developer might say, "I've never worked with ADO, but I might find out," which is not as helpful to you as the interviewer.
A more useful question would be
In what circumstances is it better to use a DataSet rather than iterating over the rows of a table?
This way you get the important stuff - actual use and technology application. They could answer in the context of Linq or SqlDataReader or whatever technology they worked with. What you get is what they understand and know how to use, not what they could Google do in a few seconds.
a source to share
I asked a similar question in a job interview, although it was probably a little taller. I asked the candidate what he likes best in Java and what he likes best in C ++. This was not some "standard question". The candidate in question, in his resume and interview, then stated the experience of both. I asked the question for two reasons. To check if the candidate actually has the knowledge they are setting out (which might be a valid reason for asking about ADO datasets / records). The second reason is for the candidate to show some degree of reflection and proficiency in his tools.
In short, the relevance of the question depends on the candidate's profile. If the candidate has declared knowledge of both, let the candidate show his understanding. If this knowledge is critical to the job, so is it.
a source to share