5 ms·

"The questions were about Linux systems administration, algorithms, computer architecture and C programming." Couldn't you just Google for the answers to these

"The questions were about Linux systems administration, algorithms, computer architecture and C programming." Couldn't you just Google for the answers to these questions in order to bring yourself up to speed where necessary? I'm not sure I see the value in trying to keep vast libraries of arcana in your head at all times.

bjelkeman-again 18y ago
Certain things goes a lot faster if you don't have to look them up evertime you have to do them. But then I haven't read the article, so what would I know? :o
nostrademons 18y ago
They ask common questions as a proxy for experience in those fields. If you work with something daily, you will end up memorizing certain facts even if you don't consciously try to. It follows, then, that if you don't have those facts memorized, you haven't been working with that technology daily.
- Retric 18y ago
  I stopped memorizing syntax a long time ago. It's been a few years and an the only thing I can recall about C's pointer syntax is ^ and & but the specifics are long gone. Not that long ago I had to look up the conditional shorthand (expression)? true: false in java etc. I have used around 12 different languages and I try and forget the stuff I am not using or I will mix and match syntax that does not work for the language I am programming in. PS: I was classified with a learning disability back in school so this could just be me.
  - nostrademons 18y ago
    It's actually * and &. ;-) Don't interview for positions in languages you've forgotten, then, or brush up and re-learn stuff before the interview. It's like riding a bike...it comes back to you. Not being able to remember pointer syntax is a serious problem if you're being hired to program in C. I can understand why they'd want to weed out anyone who can't get that, particularly given how many candidates they have.
    - Retric 18y ago
      lol, thanks. I could have said x[i] is the same as ^(x + i) and really thought that was the correct syntax. The problem is I have used enough languages and dialects that I really can't brush up on it all. I just say if it's been five years, let me break out my cheet sheet for that stuff. PS: Ok, if it was really just a C job of course I would focus on that. Edit: Dammit it is like riding a bike. I have been having C flashbacks to horrible old code. O Malloc how do I hate the let me count the ways.
      - MaysonL 18y ago
        My solution to this problem was to make up sets of editor macros for the various languages I've used, with the same key chords producing the same semantics in varying syntax.
      - ninjackn 18y ago
        Maybe it was Visual C++ you were programming in. ^ is for a handle to a object on the managed heap so it's almost the same as pointer. http://msdn.microsoft.com/de-de/library/yk97tc08.aspx http://msdn.microsoft.com/de-de/library/yk97tc08.aspx
        nostrademons 18y ago
        I was thinking it was Pascal - I think ^ is the syntax for pointers in Pascal, but the last time I programmed in that language, I was 12.
        Retric 18y ago
        Yep, pascal had ^ and @. Around 5 years ago I was spent a lot of time working with really old Object Pascal and some C code that was upgraded to OS 8/9 and then left to rot. Let me just say that low level networking code on a OS that does not have threads is a PITA. They had something like interrupts but you could not allocate memory during them. You had to first allocate using Handel's and then do something before working with actual pointers as part of your run loop and then use that memory during the interrupts. Meh, I think it might have been the most fun coding project I have ever been on, but I don't want to do that again.
quantumhobbit 18y ago
Not only that, but it seems like he was penalized for very common quick to fix errors. I'm not the best programmer ever but I always forget to initialize a data structure or forget a semicolon. I always catch the error when compiling or testing. It's like penalizing someone for a grammatical mistake. Some make more mistakes than others but no one is perfect.
strlen 18y ago
Part of the interview is an intelligence/memory/experience test. They don't want to use rigid requirements ("must absolutely have five years experience") and it would probably be illegal to administer an IQ test (and the sort of intelligence IQ measures isn't always the same as the sort of intelligence needed for the job). In addition their culture seems to be that once you're on the job (as a salaried employee vs. a contractor) they'll do all in their powers to ensure you aren't laid off, get fired or quit out of boredom: you can freely move from team to team, you generally work flexible hours and with little micro management. The tough hiring (with far too many false negatives but no false positive) requirement is why they're able to mantain such a culture.
- cmars232 18y ago
  I've heard you can freely move from team to team, but only if its one of the locally staffed projects at your office. Location makes a big difference.

bjelkeman-again 18y ago

Certain things goes a lot faster if you don't have to look them up evertime you have to do them. But then I haven't read the article, so what would I know? :o

nostrademons 18y ago

They ask common questions as a proxy for experience in those fields. If you work with something daily, you will end up memorizing certain facts even if you don't consciously try to. It follows, then, that if you don't have those facts memorized, you haven't been working with that technology daily.

Retric 18y ago
I stopped memorizing syntax a long time ago. It's been a few years and an the only thing I can recall about C's pointer syntax is ^ and & but the specifics are long gone. Not that long ago I had to look up the conditional shorthand (expression)? true: false in java etc. I have used around 12 different languages and I try and forget the stuff I am not using or I will mix and match syntax that does not work for the language I am programming in. PS: I was classified with a learning disability back in school so this could just be me.
- nostrademons 18y ago
  It's actually * and &. ;-) Don't interview for positions in languages you've forgotten, then, or brush up and re-learn stuff before the interview. It's like riding a bike...it comes back to you. Not being able to remember pointer syntax is a serious problem if you're being hired to program in C. I can understand why they'd want to weed out anyone who can't get that, particularly given how many candidates they have.
  - Retric 18y ago
    lol, thanks. I could have said x[i] is the same as ^(x + i) and really thought that was the correct syntax. The problem is I have used enough languages and dialects that I really can't brush up on it all. I just say if it's been five years, let me break out my cheet sheet for that stuff. PS: Ok, if it was really just a C job of course I would focus on that. Edit: Dammit it is like riding a bike. I have been having C flashbacks to horrible old code. O Malloc how do I hate the let me count the ways.
    - MaysonL 18y ago
      My solution to this problem was to make up sets of editor macros for the various languages I've used, with the same key chords producing the same semantics in varying syntax.
    - ninjackn 18y ago
      Maybe it was Visual C++ you were programming in. ^ is for a handle to a object on the managed heap so it's almost the same as pointer. http://msdn.microsoft.com/de-de/library/yk97tc08.aspx http://msdn.microsoft.com/de-de/library/yk97tc08.aspx
      - nostrademons 18y ago
        I was thinking it was Pascal - I think ^ is the syntax for pointers in Pascal, but the last time I programmed in that language, I was 12.
        Retric 18y ago
        Yep, pascal had ^ and @. Around 5 years ago I was spent a lot of time working with really old Object Pascal and some C code that was upgraded to OS 8/9 and then left to rot. Let me just say that low level networking code on a OS that does not have threads is a PITA. They had something like interrupts but you could not allocate memory during them. You had to first allocate using Handel's and then do something before working with actual pointers as part of your run loop and then use that memory during the interrupts. Meh, I think it might have been the most fun coding project I have ever been on, but I don't want to do that again.

quantumhobbit 18y ago

Not only that, but it seems like he was penalized for very common quick to fix errors. I'm not the best programmer ever but I always forget to initialize a data structure or forget a semicolon. I always catch the error when compiling or testing. It's like penalizing someone for a grammatical mistake. Some make more mistakes than others but no one is perfect.

strlen 18y ago

Part of the interview is an intelligence/memory/experience test. They don't want to use rigid requirements ("must absolutely have five years experience") and it would probably be illegal to administer an IQ test (and the sort of intelligence IQ measures isn't always the same as the sort of intelligence needed for the job). In addition their culture seems to be that once you're on the job (as a salaried employee vs. a contractor) they'll do all in their powers to ensure you aren't laid off, get fired or quit out of boredom: you can freely move from team to team, you generally work flexible hours and with little micro management. The tough hiring (with far too many false negatives but no false positive) requirement is why they're able to mantain such a culture.

cmars232 18y ago
I've heard you can freely move from team to team, but only if its one of the locally staffed projects at your office. Location makes a big difference.