When I interview (experienced) devs, I often ask way too generic questions. Something along the lines of "can you explain what a hash is?", without stating what kind of hash and in what context

The primary goal isn't really to explain it in detail, but to see if they get confused and ask for clarification. Way too many people just start assuming something, when a task is not defined properly. I need coworkers that push back on bullshit, and not blindly implement whatever runs along their desk, no matter how little sense it makes

If I don't hear at least one "it depends" during an interview, I don't have high hopes

[–] grendel84@tiny.tilde.website 2 points 2 days ago

@SkaveRat
in college I had a prof tell us to get into teams, then give us lego sets to assemble.

they were in the original boxes but the directions had been removed. I was the only one to go up front and ask for the directions and she gave them to me.

Apparently that was the whole point to the excersize. “ask for the resources you need"

@kamen

load more comments (35 replies)