🚀 go-pugleaf

In article <4fu7q4$95e@solutions.solon.com>, Larry Weiss <lfw@oc.com> wrote:
>Sean 'Captain Napalm' Conner wrote:
> >  That doesn't matter.  Either you follow their standard, or you don't.  If
> > you say "I have to look at it" is a sign that you may have difficulty
> > following their standards.

>Let's turn the question around.

>What are some good questions that a C programmer should ask an
>interviewer?

Since I am about to be out of work (corporate re-org) and am in
the process of interviewing, these are some of the questions I
have asked the interviewer:

1. What version/level of the compiler are you using?
   - to see if they are trying to stay current/use better tools
     then came with the OS.

2. Do you have a set of coding standards that are written down
   (or at least informal, group set, ones)?
   - if not, I'm likely to be worried about the quality/readability
     of source I'm going to have to work with.

3. Any plans for C++?
   - At this point I'm still indifferent about C++, but I want to
     know if they have any thoughts about it.  (I once worked for
     a company that had a product written in C with *1* module in
     C++ because 'well, he knew C++ so we let him use it for that'.)

4. What is the long-term outlook for the company/this project/
   C being used here?
   - It's hard to predict the future, but I want a comfort level
     that the job I want will exist for several years.  I worked
     for a large company (also see previous comment) that I thought
     would be a secure job for *many* years, only to find out that
     they were more interested in mainframe COBOL then C.

Of course, these (and more) all depend on the position/company/etc.

(btw - anyone need a good C programmer in the Chicago,IL,USA area,
I'm available.  E-mail me for more info.  Thanks.)


Jeff
--
Jeff Pleimling | jap@interaccess.com
"No, Pinky, there YOU are.  I am nowhere near that vincinity." the Brain