I agree with the premise, but it's quite painful in practice constantly probing and prodding for justification and explanation -- especially because _even with_ the justification, explanation, etc, one's mental map / the "topology" of the thing being built is only very loosely being populated as a result of the conversation. I say this having continuously tried to find a way to keep my learning rate comparable to if I was writing the code myself, and having somewhat failed.

I'm starting to wonder if the thing to address is the anxiety itself rather than the "fuzziness about the code" that creates the anxiety - and more explicitly model myself as an engineering and/or product manager counterpart to these things. I wonder how non-IC EMs/PMs do it - it seems maybe fundamentally anxiety-inducing? – but they _do_ do this already (tolerate the fact that the underlying technical system is not fully within their grasp).