News for hackers. Stuff that matters.
Re:What every PhD should know before interviewing with a tec... by rajathagasthya on Friday July 21, 2017 @02:14AM (#14818425)
> Don’t worry if you come up with a shitty answer. Just come up with something.

This is such a blatantly false statement. Nobody cares if you come up with a shitty answer in an interview. They expect working code which is optimal. You won't pass the interview if you write a naive, working solution. It's literally all or nothing. Maybe it's time companies make it clear to candidates.

Re:What every PhD should know before interviewing with a tec... by noobermin on Friday July 21, 2017 @03:29AM (#14818717)
Why is this downvoted, is it because it is too extreme?

The truth is if you can develop an optimal solution super quick during the interview, you're better than someone who can't. It might be like

optimal solution, quick > working solution, quick > no solution.

The problem is if you can't do optimal quick, then you end up spinning your wheels and end up with no solution in the allotted time.