41–50 of 53 posts
Earlier quoted context omitted.
Its not useful skill to code in a whiteboard, drawing diagrams maybe? Even that how often does it happen.
In my office, whiteboards get used all the time in design discussions and code reviews. It's a very common occurrence.
after hundreds of infosec interviews in the past ~5 years, i leave you with this gem: "describe a 'padding oracle' attack, what versions of Oracle does it affect?" this was not a trick question. i wish there was a topic: 'worst answers you've given to interview questions?' The sheer amount of interviews i have been on speaks to my epic failure here.
"How long do you plan to stay at this company if I hire you?"
I find asking a developer to write code on a whiteboard or word document to make not much sense. I was asked how many bytes are there in x amount of space, which i find as not much to do with competence in software development. A follow up question is, whats the point in asking these questions, any idea on what the goal is? There has to be an intention behind it.
Sorry, you don't see the intention behind asking people to write code on a whiteboard? Being able to lay out ideas, code, and architecture on a whiteboard is a useful skill in and of itself for communicating with coworkers, let alone using it as a way to get insight into how an interviewee codes.
"Do you brush before you floss, or do you floss before you brush?" I was so stunned and self-conscious that I might have had something stuck in my teeth to the point where after the interview I spent about a good 2 minutes looking at my teeth in the bathroom mirror. I still don't know why they asked such a question. What would they have asked the next person? "Do you fold or scrunch toilet paper" ?
I would also ask how he interprets the answers.