|
>> What if the poor fellow doesnt even know what a linked list is?
Then he doesn't get the job, because he isn't qualified for the job. If a candidate doesn't know basic data structures, then he (or she) needs to go learn. But not on the company's nickel.
|
|
|
|
|
u missed the point. he may know what it is...
Ill give u an example:
I had a friend of mine who was a great programmer and he learned it by himself. He mastered all the basic structures, bla bla bla but he didnt knew some of their names. For example, instead of knowing what an 'array' is, he knew what a 'vector' is. So, if you ask a guy to perform some kind of operation on an 'array', he wouldnt know for a start what an array is, as he knows it as a 'vector'.
Remember that English is not the first language for most of the world, so sometimes people dont get the ideia cause they dont understand the basic mean of the word. For example, it took me a while to realize what the name 'thread' meant (it has no relevant translation to my native tongue), although i perfectly knew how to use it. If it was called 'dog', it wouldnt make a difference to me, as i knew what it was for, and, because of my poor english, i would'nt try to associate it with a meaning right away.
|
|
|
|
|
I don't believe it's possible to be fully versed in data structures and not know the term array, especially if one already knows the term vector.
I'm not saying companies shouldn't make some allowances for non-native English speakers, but that's overboard. In case you haven't noticed, all major programming languages use English class names. The name of the Thread class doesn't change if you program in Spanish or Italian. (I might could see the confusion with the word "array", since it's rarely used explicitly in code, but not linked list.)
With very minimal proding, it should be possible to get any semi-skilled programmer to explain the workings of a linked list. Otherwise, I must again say that he or she is not skilled enough. Anyone who has done any sizable amount of work will know the basic ADTs.
|
|
|
|
|
As one of the lead developers I do interview all new candidates to add to our team. I think a lot can be learned in an interview more than just the yes / no questions. I usually ask a lot of do you know... What kind of ... Did you ... These questions hold some value but you are sometimes not sure if they are telling the truth. But then I get into discussing what I do and that is where I learn the most about what a candidate actually knows. If they have no clue what I am talking about it is usually very easy to tell...
John
|
|
|
|
|
If it were up to me (clearly it's not  ), I'd rely mostly on internships and contract/temp positions. You can then evaluate somebody more realistically after a few months of actual work than you can in any type of interview.
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
Yeah very true, this is a very good solution, I was hired on a contract position for a period of six month, I was not sure wheather my contract would be extended or i will be back at home without any job. So i attened interviews and got selected in one of the top company in India. My present company didnt want to loose me so they offered me a permanent post and good salary increase
MSN Messenger.
prakashnadar@msn.com
|
|
|
|
|
Besides interviewing the development candidates and giving them some questions to answer, I also like to get to know what kind of person they are, such as if they like to explore new ideas and research on their own time because they're truly interested, or if they think that what they learned in couple classes is all they need to know (which is utter BS). Unfortunately, the former seems to be harder to come by these days, but since we're a growing company trying to stay on the cutting edge, it always pays off.
There has been once or twice that the CEO or CFO has forced me to hire an intern because they are cheap or free (over someone that we'd have to pay a little more) and it never fails that these people have no ambition to learn more and just don't really get it (i.e., development and practices). I typically waste more time (which is money) "babysitting" these people than the difference in wages.
Microsoft MVP, Visual C#
My Articles
|
|
|
|
|
Heath Stewart wrote:
There has been once or twice that the CEO or CFO has forced me to hire an intern because they are cheap or free (over someone that we'd have to pay a little more) and it never fails that these people have no ambition to learn more and just don't really get it (i.e., development and practices).
Sounds like you need to apply the same practices you use to weed out bad full-time candidates. Sure, there are a lot of lazy [and|or] clueless people looking for internships - there are also a few of us who have the knowledge and the drive, but whose Work Experience resume section is a tad thin. Better yet, if you make a mistake, it's often a lot easier/cheaper to be rid of a bad intern than a bad FT employee. 
How do you move in a world of fog, That's always changing things?
Makes me wish that i could be a dog, When i see the price that you pay.
|
|
|
|
|
About 1 or 2 interviews, the rest is a trick question as posted and some of the famous "Person Reading Algorithm", to see if this person is the ONE....
|
|
|
|
|
Never thought it was so hard to read applicant's mind: They want a job
Norman Fung
|
|
|
|
|
Norman Fung wrote:
Never thought it was so hard to read applicant's mind: They want a job
MSN Messenger.
prakashnadar@msn.com
|
|
|
|
|
How would you fare ?
// What is the output of this function call ?
//
// foo("box");
//
void foo( const char* title )
{
char* my_title;
strcpy( my_title, title );
strcat( my_title, "." );
MessageBox(NULL, my_title, "z", MB_OK);
}
// Note that only 1 out of 5 interview will answer correctly.
// interview with candidates fresh out of school.
|
|
|
|
|
Erm, undefined..
Is that meant to be a trick question?
Ryan
|
|
|
|
|
I would say
Access violation.
Illegal write to 0xxxxxxxxxxxx
|
|
|
|
|
Won't it crash? my_title is never new'd up. strcpy assumes that memory has already been allocated for the target.
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
Of course, Access violation, crash or undefined are all acceptable answers.
Still, I can differentiate those who think that memory is just magically there
from those who know better. At school, they learn to use "string" or CString,
but before long, they will need to know a little more of what's going on
under the hood.
I am not surprised that those who post on this forum have the proper answer.
Newbies will not. Often, I can tell the value of a candidate by watching them
recover after they realize their mistake. I ask a supplemental question such
as "where does the memory for new_title come from ?
Those that never catch on are better left to VB shops...
|
|
|
|
|
I miss const functions (I use C# now). 
"You can have everything in life you want if you will just help enough other people get what they want." --Zig Ziglar
|
|
|
|
|
Besides that, shouldn't we be using strncpy and strncat to be safe?
|
|
|
|
|
.. shouldn't you be using wchar_t or TCHAR here? Come on, man, we don't program in an English-centric world anymore, gotta worry about those non-ASCII characters. 
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
I prefer to stick to old style "c" types as a basic interview foundation.
Of course, when I start working with newbies, I insist on "bool" (not BOOL), TCHAR (not char), LPCTSTR (not const char*) as well as const correctness, assertions and 1,000,000,000 little bits and pieces that make the code clear and fun to read.
Navin wrote:
Come on, man, we don't program in an English-centric world anymore, gotta worry about those non-ASCII characters.
Actually, I speak french and it so happens that french, like most western countries have managed to map their character set in the 8 bit address set of ASCII. (extended ascii, if you prefer, since pure ascii is a 7 bit)
So it's not a question of English-centric world, it's a western hemisphere centric world 
|
|
|
|
|
Bamaco2 wrote:
I insist on "bool" (not BOOL), TCHAR (not char), LPCTSTR (not const char*)
bool and not BOOL, fine, but at the same time LPCTSTR instead of const TCHAR* (LPCTSTR is not a const char*, notice the "T" in LPCTSTR :P )
Well, Instead of the Win32 define thingy BOOL you use bool, I agree there, but instead of a const char* you use the Win32 define LPCSTR, hmmmm, very much not consequent I would say 
- Anders
Money talks, but all mine ever says is "Goodbye!"
ShotKeeper, my Photo Album / Organizer Application[^]My Photos[^]
|
|
|
|
|
Anders Molin wrote:
LPCTSTR is not a const char*, notice the "T" in LPCTSTR
Well, if you want to get technical...
LPCTSTR IS const, and will default to a LPCWSTR if UNICODE is defined.
LPCWSTR is a pointer to a const null-terminated string of 16-bit Unicode characters.
(both of which being null-terminated of course)
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
|
If you're going to be hard coding all the strings, there's no real reason to be using anything other than char arrays, is there? I find that the hassle in making code international typically comes from hard-coded values, rather than hard-coded types. A little time spent with the replace function of any text editor can convert code to use TCHAR or wchar_t, but there's no simple way to extract all the hard-coded strings into properties or resources files. So far as I know, at least.
|
|
|
|
|
I try to make my code independent of char size
by using the _T() macro for my constants.
This way, when unicode is defined, characters are taken as 16 bit values,
otherwise, the compiler uses 8 bit values.
Most of the output on the GUI can be covered this way.
I work a lot with microcontrollers, where most of the type I handle are not
"compiler optimal" but have a pre-defined width.
My code is full of "uint8" "int8" "uint16" "int16" "uint32" "int32" and "uint64" "int64"
then I usually #include "ProjectTypes.h" where those symbols are typedefed. I hardly
ever handle strings, except for quick and dirty debug strings. Those stay 8 bit wide.
that's for the microcontroller code and for the PC code interfacing with shared structures between PC and microcontroller.
Actually, I like to pass const CString& around as function parameters (in windows, anyway.
I never deal with CString like objects in my microcontroller code.
Instead, I might have something like this:
#ifdef _TRACE_THIGNY<br />
char temp[40];<br />
sprintf(temp,"x=%d. y=%d. z=%d", (int)x, (int)y, (int)z);<br />
SendMsgString(temp);<br />
#endif
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
