3 ms·
I had an interview recently where we did something similar and it was awesome. They had picked an especially good example: the code was small enough that it did
by wpietri 11y ago
I had an interview recently where we did something similar and it was awesome. They had picked an especially good example: the code was small enough that it didn't take long, but it has a variety of sorts of badness, from coding errors to bad names to bad method grouping to logical errors.
I'm definitely stealing this trick.
- azundo 11y agoI wrote one of these for my work as well. Definitely our go-to for getting a sense of how well people can understand others' code and how they think about data modeling/complexity. A very small initial page of code can go a long way.