|
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
|
|
|
|
|
That is true, the toughest part if i18n is collecting all those strings that need to be translated and putting them in text/resource files. However for any strings that don't need translation, or any other hard-coded string, _T() and TCHAR still apply, in case you want to be able to compile your app in both Unicode and ASCII.
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
You can use non-ASCII characters in regular char strings. It's a little tricky with languages that use multi-byte charsets, since you have to worry about lead/trail bytes, but it's definitely possible.
For the most part you only really NEED Unicode when you're mixing vastly different languages within strings, like russian and chinese.
|
|
|
|
|
Bamaco2 wrote:
// What is the output of this function call ?
//
// foo("box");
//
Well actually nothing will happen. The call to foo is commented out
|
|
|
|
|
Nothing - it's declared as void.
No-one seems to have mentioned it yet, so I would suggest using STL strings/wstrings and stringstreams/wstringstreams to avoid that sort of memory problem.
Gavin Greig
"Haw, you're no deid," girned Charon. "Get aff ma boat or ah'll report ye."
Matthew Fitt - The Hoose O Haivers: The Twelve Trauchles O Heracles.
|
|
|
|
|
I can't imagine hiring a c++ programmer at our company, a c# programmer maybe, but c++? Not unless we wanted someone to take over the "back catalog" updates.
There is much to be said in favor of modern journalism. By giving us the opinions of the uneducated, it keeps us in touch with the ignorance of the community.<br />
- Oscar Wilde<br />
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
