justin = { main feed , music , code , askjf , pubkey };
Ask Justin Frankel
No reasonable question unanswered since 2009!

Suggested topics: programming, music, sleep, coffee, etc.

Note: please do not ask questions about REAPER features, bugs or scheduling, use the forums instead.

Name: Ask: Human (enter yes):
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Question: On Thursday i have a technical job interview for the position of embedded C/C++ programmer; Any tips or advise?
Asked by _gio (62.103.65.x) on October 26 2009, 12:24pm
Reply on October 26 2009, 1:44pm (edited at October 26 2009, 1:46pm):
    Hmm, I dunno.

    The biggest thing, is be personable and reasonable. Most issues I've had with other programmers are either that they aren't good at communicating, or they are stubborn in their own ways, or aren't willing to work in the style of existing code. Little things, like where to put the {, can make a big difference -- let alone using different design styles.

    If I was looking to hire someone, I'd look for some of the following:
    • Love and passion of pointers
    • Love of OOP design in C++, but disdain for over engineering. Distrust operator overloading, avoid if humanly possible multiple inheritance, etc.
    • Desire for simple elegant and reusable code when it makes sense, but willingness to copy/paste and get things done.
    • General loyalty to a primary development language, but ability to appreciate and use other languages when appropriate (i.e. scripting languages have their places and are hugely useful).
    • Willingness to iteratively design -- i.e. revise design until it meets goals, maintaining existing function during the transition.
    • Wisdom not to throw away existing code and "rewrite". I will concede that starting over can be useful, but it needs to be very carefully done, and if all possible iteratively and done by sections (i.e. starting from scratch when duplicating existing behavior = BAD). Rewriting a module, getting it to function within a complete system, and being able to test it within that functioning system = WIN.

    These attributes reflect my philosophy, obviously, but to the extent you find that you agree with them, it might be worth embracing them.
Comment:
    Your Name:   -- Site Owner's Name:  (for human-verification)

    Comment:
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Copyright 2025 Justin Frankel. | RSS