Takes about 15-30 seconds to figure out if the person you are talking to understands or is being evasive. In which case you need to adjust and put on kiddy gloves, slow down, and coax information out.
> Takes about 15-30 seconds to figure out if the person you are talking to understands or is being evasive. In which case you need to adjust and put on kiddy gloves, slow down, and coax information out.
Personally I don't find this approach very helpful. It's not always clear to me whether the person Im talking to does not understand the topic thoroughly enough, or whether they actually understand it much more deeply than I do and it's actually more complicated than I currently appreciate. Going in with an open mind is important imo.
I find this to be particularly true with software engineering questions, where a lot of the time you're making a series of compromises based on some assumptions about the use case. Maybe they don't understand a particular piece of code, or maybe it's that they've just spoken to a user who's doing something weird and they're trying to work out how that use case will interact with this code.
Takes about 15-30 seconds to figure out if the person you are talking to understands or is being evasive. In which case you need to adjust and put on kiddy gloves, slow down, and coax information out.