this post was submitted on 12 Feb 2024
754 points (97.4% liked)
linuxmemes
20744 readers
846 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's fine if there are no weird pedantic ropes to fall over. I am not a compiler or linker, that's what I have compilers and linkers for. Same with an IDE. I don't know many details of the stdlib or other common libs, because why should I waste space in my brain for stuff code completion can show me...
The kind of bugs I'm talking about are things like "the logical flow of the code is broken because the order of the if/else if/else branches is wrong", "this program never finishes because you don't increment that counter" and "you specified print the numbers 1 to 100, but that counter starts at 0".
I'm testing your ability to think logically, not your knowledge of stdlib trivia
No, that approach is completely fine even if pedantic because you get the candidate to reason about their choices and their approach which tells you so much more about them than rote memorization. Being pedantic is the whole point of it.
That's likely not what I mean by pedantic. If your code example has syntactic errors or calls functions with not enough or too many parameters and you expect them to notice, you want them to do, what a compiler does or to know technical documentation by heart. Which is completely academic and pointless.
Concentrating on "algorithmic" solution at hand is fine, though. Unless you again expect them to recognize stuff like "hey this is almost Dijkstra's algorithm but wrong", because the interview should not be a university computer science test.