3 ms·
Think of it as a slightly less insulting form of FizzBuzz. I regularily used a similar exercise to weed out bad candidates. The task was to build a stack with
by danielh 10y ago
Think of it as a slightly less insulting form of FizzBuzz.
I regularily used a similar exercise to weed out bad candidates. The task was to build a stack with based on a double linked. Looking up stuff was okay, but straight copy paste was not. I gave them half a day and told them to write the best code they can.
There where many discussions how that exercise is relevant to the junior PHP dev position we were hiring for (spoiler: it's not). But it gives you a good idea what the candidate considers good code (consistent code style, documentation, tests,...)
- lettersdigits 10y agoI'm curious about the stats (if you have them): how many of the candidates added documentation ? because one could argue that documentation by itself is not DRY since now you have both the code and the description of the code (the docs). if the code changes - you MUST change the docs as well (otherwise the docs and the code are not overlapping, which is much worse than not having docs in the first place). I might be completely wrong about documentation not being DRY, but this by itself could be a good conversation with a candidate .