[GoForthAssemble]

A bit sideways from topic but; I got grilled by the head of the Euro fighter project (Ford management) on the importance of using arrays for everything. Don't do 'int a;' always create an array. I was dismissed half way through for not agreeing.

[JohnFen]

> I was dismissed half way through for not agreeing.

Even if I got an offer out of that interview, I would have turned it down. The head of the project making such a statement (in the absence of a good reason for the stance) is a big red warning flag.

[jb775]

What was the argument for always creating an array?

[pipingdog]

The point of the question, I imagine (and am giving the interviewer the benefit of the doubt), was to see how the candidate negotiated technical compromises. Merely disagreeing without exploring the reasoning behind it and perhaps finding a different solution together might be a red flag for that environment.

[GoForthAssemble]

The guys who were originally going to do the interview were in the room. Squirming. I asked if his background was APL (you know array based stuff) and was told that APL, and I shit you not, 'was not A Programming Language'.