3 ms·
I like the idea, might not bother with the whole "actually execute it to see if it produces the expected result" thing, but otherwise it slots into the "so obvi
by wizofaus 4y ago
I like the idea, might not bother with the whole "actually execute it to see if it produces the expected result" thing, but otherwise it slots into the "so obviously a good idea I can't believe I hadn't thought of it before". I can't say I've ever been asked in an interview to review a piece of code and predict what bugs it might have etc., but it's definitely a skill I use on the job all the time.
- fjdbeb76 4y agoI did this when I looked after interviews. I'd print off a piece of legacy code that was particularly ugly and ask them to review it. I'd tell them I wasn't looking for silly stuff like parser errors and instead was just looking for their opinion on the code. How they thought it worked and how they would improve or do it differently. It was mostly just an interview prompt with a consistent starting point that lead to interesting insights about the interviewee but generally had repeated talking points across candidates.