Interview Tip

Hmmm, my suspicion is that you are exaggerating your experience. I think it should be obvious to anyone who has used C++ for 4 years and C for 1 year that C is a subset of C++.

Well I have a computer studies degree whereby we were taught C++, I completed a placement year developing applications in VS 6.0, specifically using C++ - OO etc.
I''ve just completed an MSc in computer graphics, programming various applications in pure C.

Yes C++ expands the concepts of the C language, but to say one knows C++ doesnt mean that they can claim to be fluent with the in''s and out''s of the C language.

So I wouldn’t say I was exaggerating.

JohnBolton I think not. I think it should be obvious to anyone who has used C++ for 4 years and C for 1 year that, while C is a subset of C++, there are many differences.

Firstly, think in C. It may sound obvious but I have seen that many C++ coders tend to want to use features not present in C, so know what''s available to you and what isn''t. Some tips:
- pointers vs. references (no references in C)
- NULL vs. 0 (NULL is the convention in C, 0 in C++)
- true/false defferences between C/C++
- C libs vs C++ libs (printf() instead of std::cout, etc.)

Secondly, C design methodology is vastly different than C++ style OOP. However, good C code tends to be, as much as the language will allow, object oriented. Mostly this is done by organizing your source files into a sort of hierarchy. I''m sure you know that files, like C++ classes, should be responsible for a single task.

Good luck with your interview.

Ravyne, NYN Interactive Entertainment
[My Site][My School][My Group]

I agree with you mantra, try working on brushing up on your C formatting style, you can usually tell a C programmer immediately by that alone.

If they want strict C experience... try making some programs in C..not just syntax, but style... get used to procedural AND object oriented C... no classes though. Also, make sure you remember the little nuances between C and C++.. like putting all the variable definitions at the beginning of the function and stuff... they probably don''t want that if they want to maintain code in strict C...

As for the interview? Ask questions... I am very guilty of not asking questions and it has lost me a few nice job oppertunities. On the other hand.. don''t ask stupid questions.. or irrelevant questions.. the more intelligent and relevant the question, the more points you will score with the interviewer. Also, don''t be nervous.. but don''t slouch either.. definitely don''t slouch. Always be sure to shake hands with the people you meet, at the beginning and at the end... and make sure it''s a firm grip.. it doesn''t have to be hard, but just firm.. infer from your grip that you couuld put much more power into it if you need to.

Also, don''t lie during the interview... if you''re not really good at fibbing, they might be able to pick it out.. and if they ask you again and your story changes.. BAM! That shouldn''t be a problem.. but even things on technicalities.. like, don''t exaggerate things.. if you have, for example, a year of pogo sticking school.. don''t say that you have a year of pogo sticking experience.. they will always ask about what your experience makes up.

Always be sure and confident.. even if you screw up, don''t let them know it..

done ranting.. good luck

---

Disclaimer: "I am in no way qualified to present advice on any topic concerning anything and can not be held responsible for any damages that my advice may incurr (due to neither my negligence nor yours)"

Be yourself. Everything will work fine from there.
It''s worked for me so far anyway (2 interviews, 2 job offers ).
But to expand on what falkone said...
If you be yourself, there should be no need to be nervous, you''re not trying to prove anything.
... there should definitely be no need to fib!
Employers want to get an idea of you as a person as much as get an idea of your technical ability. They will be having the pleasure of your company after all, so you need to show them what it will be like working with you. Experienced HR people will know straight away if you are being sincere or not.

As far a C goes, i''d mostly be brushing up on using standard C libs (stdio.h, stdlib.h) etc. these contain the major differences in functionality as far as i''m concerned.
CYer, Blitz

C++ experience where 4 years of C experience is required should be fine!

For a junior role you''re simply expected to cope with the workload - asking a more senior programmer for advice on how to do something is actually good practice - it shows you''re willing to share problems with those more qualified to solve them.

Generally that means that as a junior, as long as you can do the work, you should be ok.


Maths is good btw.