34 ms·

seems like a silly gotcha -- a literal technicality. Aren't you worried you passed on some amazing talent because they didn't read the same "bibles" or study i

• Clubber 9y ago
  You literally couldn't program in Delphi if you didn't know that.
• Stratoscope 9y ago
  Sure, if you were hiring someone with no Delphi/Pascal experience, for example a programmer who had worked in multiple languages and you expected to be able to learn Delphi quickly, then it would be a silly gotcha. But if you were interviewing someone who claimed to know Delphi/Pascal at all and didn't know this off the top of their head, it would be a big red flag. It would be like asking a C programmer what's the difference between "void foo(){...}" and "int foo(){...}". They had better be able to tell you the difference without having to think about it.
  • Clubber 9y ago
    It's funny. Based on the responses, I can tell who has Delphi experience and who does not. Pretty good interview question for Delphi devs, I'd say. :) Sure beats 5 hour interviews about God knows what.
• marcosdumay 9y ago
  If you were programing in Pascal for 5 minutes, you would know the answer. It is a technicality, but a plainly accessible one. If "knows Pascal" is one of the job requirements, it's actually a good question.
• mikestew 9y ago
  I haven't touched Delphi in twenty years, and I still remember the difference. It's fizz-buzz for Delphi devs: if you say you're a Delphi dev and don't know this off the top of your head, then you're lying about your experience.