Journal Chacham's Journal: Chronicle: Helped interview a candidate yesterday. 12
So, we had an interview. I asked most of the questions. Two things stood out above the rest.
He had stated his knowledge with VB and VB
He began to shake. He started asking about the SQL involved to get the data. I told him the dataset already has it. He said he couldn't put down actual code as he was not in front of a computer. I told him not to worry. He said he could give pseudo-code. I told him it was all-right. He must have been sweating bullets, and i began to regret asking him what i thought was a simple question.
He answered that in VB 6 he could use a Select Case statement on the date, and have the individual cases decide the color like for due date being less than today's date. He mentioned that he could also use an If. Fair enough. Indeed a case would be better given the date comparison has three states. Fine. I asked how the
The "correct" answer, that i would expect, would have been DateA < Now() for VB6, and DateTime.Compare(DateA, DateTime.Today) < 0.
Basically, that the comparison is a method of the date object, as opposed to an overloaded less-than operator. Although, the comment on the convert was something.
So, i asked him for a short description of
Well, he seemed to know how to code in
I must not be cut out for interviews. I seem to ask the wrong questions.
Well, i finished, and i asked him if he had any questions for us. Nervously, he pulled out a sheet of paper with some questions he had prepared. Very nice. He asked what three things we were looking for to fill this position. My supervisor answer the questions in detail, and at a pause, i added in a "fourth" item. Realizing i needed to calm this guy down, i told him that the position requires the person to like cherry coke and jalapeno Krunchers. He started to smile and explained that he liked jalapeno flavors and spoke for a moment about it, when all of a sudden the comet hit. "KRUNCHERS!" he exclaimed. He went on to tell us that no matter the flavor he liked Krunchers. Well, i guess i hit a home-run with that one.
We were eating the green bag this morning, and the account manager for yesterday's interviewee walked by. Asking how it all went, my supervisor asked him if he liked jalapeno krunchers, he said he'd try one, because he liked krunchers, and then later asked "krunchers?" he think he might get a bag on the way to the office. Methinks the anecdote was already related, but, who knows?
VB6 vs. VB.Net (Score:2)
Man, at one time I could give you twenty things that really sucked about what they did with VB.Net. I spent about 6 months on a project to automagically convert our QB code (procedural driven) into VB6 (event driven). It was an amazingly fun challenge. It was great!
Then, shortly after that had finished, gone through Q&A, and got released into the general public, MS came out with VB.Net. (Well, .Net in general.) The logic that would be required to convert from VB6 to VB.Net would have been significantl
Re: (Score:1)
Thanx for the anecodte.
Date comparison (Score:2)
Re: (Score:1)
That is true, and it is backwards compatible with the old VB way of an overloaded less-than operator. It is not the
A VB programmer can code in
Re: (Score:2)
Re: (Score:1)
There are two points i want to make, however.
1) The less-than operator is overloaded to work with dates. If date was a string, year would have to be first to compare. Further, not every language will allow this form of overloading.
Using the object's method, however, does not rely on overloading (which makes it abundantly clear), is cross-language and cross-platform (as long as it supports
what's the position for (Score:1)
Were you guys looking for someone who can theorize about language design and marketing approaches, or one who can get something done?
It sounds like it must've been for a Director of Technology position.
Re: (Score:1)
Neither. We were looking for a
Anyway, i don't make the decisions, but i was brought in to help surmise the candidates technical side. He said he knew VB and VB
Re: (Score:1)
It sounds like you don't know much about this stuff. I don't either, I did some VB6 for a short while, but haven't touched any
Re: (Score:1)
I started with VB 3, and i just did a read-only conversion of a project from VB 6 to VB
Re: (Score:1)
Even if the
Re: (Score:1)
That was mostly additions. Note, VB 3 fit on a floppy, and was a great basic program. VB 5, with its compilation of the executable, and COM, as you mention, created a VB 6 that supported interfacing with just about everything, and could be used easily. So it included a wider audience, and that would be the major difference.
Even if the