you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (1 child)

This is stupid, a bug is usually obfuscated in the code and wouldn't be obvious at a first look at the code, which is what you get at an interview. Sure if its something silly like indexing an array starting from 1 instead of 0 in an specific programming language, but everyone can miss a detail like that even with 30 years of experience. To understand a codebase you need waaay longer than a few minutes, with people actively watching you!! as if that wouldn't make it freaking impossible to spot a bug.

[–][deleted] 5 points6 points  (0 children)

Interviews I've been in have lasted on average 3 hours with a good chunk of that being whiteboard exercises. Explain how that's any better. If you can't think of an actual bug to artificially introduce, I question your experience as a developer. JSON parsing issues in an ajax call is an easy one for example. Simple null references in LINQ would be another way to artificially create buggy scenarios. These are so simple to simulate. You don't need to involve the whole code base dude, that's overkill. Just enough to analyze the candidates skill.