4 ms·
I recognize that. My colleague would say, I'm fixing that in the docker. Then i ask (somewhat frustrated) 'the dockerfile, the docker image or the docker contai
by nuancebydefault 3y ago
I recognize that. My colleague would say, I'm fixing that in the docker. Then i ask (somewhat frustrated) 'the dockerfile, the docker image or the docker container?' Then he answers (somewhat frustrated) 'that's a detail I don't want to go into now.' And I understand it like, 'damn I didn't even think about that, i just fend him off'. My other colleague, who has great empathy, says: "you are very blue, he's very red".
- fragmede 3y agoI'm not sure what blue vs red is, in this context, but I can't tell if the frustration is because your colleague thinks you're asking because you don't understand docker, or because you question their understanding of docker.
- nuancebydefault 3y agoI know he knows docker well enough, but somehow he finds something a detail, where i find that difference important. That said, i do get what you're saying, indeed this might be the issue.
- ivix 3y agoIf it's a detail to them, they might be looking at a bigger picture than you are.
- PH95VuimJjqBqy 3y agoI'm going to echo what the other poster just said. If I know something is a solvable problem, I don't worry about it, it's just a detail. For example, if I have to integrate with a 3rd party API, the details don't matter until I get there. I have full confidence I'll be able to do that even if it's a super old school strings over tcp before XML was a thing. Because I'm fully confident in being able to solve that, I don't care about it, it's just a detail, like having to reverse your vehicle out of your driveway. It may even be that he's not completely sure of the details yet but he's confident he knows the approach to take and he'll do the discovery while he's working the problem.
- nuancebydefault 3y agoThanks for the feedback!