Hacker News new | past | comments | ask | show | jobs | submit login

All kinds of ideas are apt to come when you are in the shower... ideas for simplification, ideas for improving performance, ideas for new features. That doesn’t mean we should incorporate a shower in the interview schedule! We can simple review the interviewee’s code prioritizing simplicity over things like did he/she consider every corner case.



> We can simple review the interviewee’s code prioritizing simplicity over things like did he/she consider every corner case.

That sounds like a recipe for disaster, though. Simplicity that doesn't account for every corner case in the domain of the code[0] is false simplicity, a bad abstraction. The challenge of writing simple code is this: threading a single, unifying concept through all corner cases.

--

[0] - I.e. when writing a function, you don't necessarily have to account for e.g. the off chance of heap getting corrupted externally in the middle of execution of your code. But you'd better account for all the values your function might be called with, in all combinations.


>threading a single, unifying concept through all corner cases

Some corner cases influence the core algorithm some don’t. Checking for degenerate cases and so on may not influence the core algorithm, if so need not be done in an interview.


An interview doesn’t allow for any digestion, it is pure performance, either follow the proper practiced steps correctly, or fail.

Your approach is just more of that.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: