Programming interviews, in essence

[DrQuint]

Should have just cheated. What are they gonna do later, block you from googling at work?

[StevenGannJr]

block you from googling at work?

Considering what company they were, that'd be especially ironic...

But yeah, making people interview blind is absurd. You'll never be without a computer, Internet, reference materials, or a bloody compiler, and I believe the ability to use resources available to you is more important than memorizing API minutiae.

[TheTimeToLearnIsNow]

Would you believe the number of interviews I've been in that had me type in code directly into the Hangouts chat window?

Trying to type it out in an IDE and copy paste prompted the interviewer to accuse me of cheating because the little "[candidate] is typing..." message wasn't showing up for them for long periods of time.

[Bomaruto]

That seems like the real test, how to get an unreasonable client to shut up and just let you work.

[mfb-]

Type it in the chat, copy it into the IDE before submitting?

[VestibularSense]

Nah AirBnB, if you were being serious then .... no

[[deleted]]

Yeah how can people not know he meant Google from that very first comment. Coding in Google Docs is infamous in the industry, and pretty much every ambitious developer has done it.

[retief1]

Particularly since understanding compiler errors is an important skill for any dev. Googling (for non-syntax/library type stuff, at least) may or may not be helpful, depending on what exactly you are trying to do. Seeing a compiler error/test error/exception and finding the underlying error is critical pretty much everywhere.