4 ms·

in my book that'd be a bad answer. thats just a lot of words for "no I don't know". I'd rather being told "no I don't know, but I'm willing to find out if neede

in my book that'd be a bad answer. thats just a lot of words for "no I don't know". I'd rather being told "no I don't know, but I'm willing to find out if needed"

sanderjd 9y ago
This is why we can't have nice things :-) You seem to be looking for technical details, where I'm looking for a mental model that displays understanding. The parent's post is "this is how it works", and you want "this is how it is implemented". Someone interviewing has no idea which of the two of us they are talking to. That's why the technical interview process is so fraught.
- dixie_land 9y ago
  I think the context is important. My comment was assuming a technical interview. It is implied in this context "how" means how it was implemented rather than how to use it. Otherwise the question would be phrased more explicitly "how to use db indexes to (optimize performance, etc.) For instance if I were an auto repair shop owner asking a technician candidate "do you know how a small block ford work" I meant how the manifold, heads, rotary etc. fit together rather than how to drive a kick ass street rod (which is cool but not the skill I'm interviewing you for)
  - sanderjd 9y ago
    To continue your car analogy, I think the question about indexes is more like asking "how does a piston work?". For me, it would be more important to display a strong mental model of the role a piston plays in the overall function of the engine and how it does its work in general than to know technical details about different real pistons in different real engines. It seems like you feel the opposite, which is also valid, just different. My point was really that a major reason interviews are so daunting is that candidates don't know whether they're talking to someone like you or someone like me.
    - dixie_land 9y ago
      That's a good point. I think I'll be framing my questions more explicitly when a particular skill is wanted

in my book that'd be a bad answer. thats just a lot of words for "no I don't know". I'd rather being told "no I don't know, but I'm willing to find out if needed"

sanderjd 9y ago

This is why we can't have nice things :-) You seem to be looking for technical details, where I'm looking for a mental model that displays understanding. The parent's post is "this is how it works", and you want "this is how it is implemented". Someone interviewing has no idea which of the two of us they are talking to. That's why the technical interview process is so fraught.

dixie_land 9y ago
I think the context is important. My comment was assuming a technical interview. It is implied in this context "how" means how it was implemented rather than how to use it. Otherwise the question would be phrased more explicitly "how to use db indexes to (optimize performance, etc.) For instance if I were an auto repair shop owner asking a technician candidate "do you know how a small block ford work" I meant how the manifold, heads, rotary etc. fit together rather than how to drive a kick ass street rod (which is cool but not the skill I'm interviewing you for)
- sanderjd 9y ago
  To continue your car analogy, I think the question about indexes is more like asking "how does a piston work?". For me, it would be more important to display a strong mental model of the role a piston plays in the overall function of the engine and how it does its work in general than to know technical details about different real pistons in different real engines. It seems like you feel the opposite, which is also valid, just different. My point was really that a major reason interviews are so daunting is that candidates don't know whether they're talking to someone like you or someone like me.
  - dixie_land 9y ago
    That's a good point. I think I'll be framing my questions more explicitly when a particular skill is wanted